Mobile
Mobile
Section titled “Mobile”This page is generated from the live QualityMax MCP registry. Examples use placeholders; replace them with values for your workspace.
get_mobile_audit_evidence
Section titled “get_mobile_audit_evidence”Purpose
Section titled “Purpose”Return the screenshot URLs and bounded scanner evidence for a completed Mobile Readiness Audit. Use this before Claude writes a qualitative report.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
audit_id |
string |
Yes | Completed mobile audit ID |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "audit_id": "your-audit-id" }, "tool": "get_mobile_audit_evidence"}get_mobile_audit_status
Section titled “get_mobile_audit_status”Purpose
Section titled “Purpose”Get status, score, and report path for a Mobile Readiness Audit.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
audit_id |
string |
Yes | Mobile audit ID |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "audit_id": "your-audit-id" }, "tool": "get_mobile_audit_status"}list_mobile_audits
Section titled “list_mobile_audits”Purpose
Section titled “Purpose”List Mobile Readiness Audits for a project, newest first.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
project_id |
integer |
Yes | Project to inspect |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "project_id": 1 }, "tool": "list_mobile_audits"}parse_mobile_audit_report
Section titled “parse_mobile_audit_report”Purpose
Section titled “Purpose”Convert extracted text from a QualityMax-style mobile audit PDF or HTML report into structured findings: ID, severity, surface, breakpoints, root cause, and fix prompt. Use the result to create or link follow-up work; this tool never changes project data.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
report_text |
string |
No | Text extracted from the mobile audit report. Provide exactly one of report_text or report_pdf_base64. |
report_pdf_base64 |
string |
No | Base64-encoded mobile-audit PDF. Provide this instead of report_text when the source is a PDF. Provide exactly one of report_text or report_pdf_base64. |
source_name |
string |
No | Optional report filename or label |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": {}, "tool": "parse_mobile_audit_report"}render_mobile_audit_report
Section titled “render_mobile_audit_report”Purpose
Section titled “Purpose”Store a structured BYO-Claude mobile-audit report and render a shareable HTML report plus a downloadable PDF. This does not call a QualityMax model.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
audit_id |
string |
Yes | Completed mobile audit ID |
report |
object |
Yes | Claude-authored report with title, executive_summary, and findings. Each finding requires id, title, severity, and surface; optional fields are breakpoints, observation, root_cause, fix_prompt, and evidence_url. |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "audit_id": "your-audit-id", "report": {} }, "tool": "render_mobile_audit_report"}share_mobile_audit
Section titled “share_mobile_audit”Purpose
Section titled “Purpose”Create or return the public share link for a completed Mobile Readiness Audit.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
audit_id |
string |
Yes | Completed mobile audit ID |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "audit_id": "your-audit-id" }, "tool": "share_mobile_audit"}start_mobile_audit
Section titled “start_mobile_audit”Purpose
Section titled “Purpose”Start a detailed Mobile Readiness Audit for a project. It captures responsive evidence at 1440px, 768px, and 375px, checks console/link/accessibility/layout risks, and prepares a shareable report. Uses the project main_url unless url is provided.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
project_id |
integer |
Yes | Project to audit |
url |
string |
No | Optional HTTP/HTTPS URL override |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "project_id": 1 }, "tool": "start_mobile_audit"}update_mobile_flow
Section titled “update_mobile_flow”Purpose
Section titled “Purpose”Update a managed mobile script from its canonical QTML mobile flow. Validates the flow and platform, rejects stale revisions, increments the revision, and deterministically recompiles the executable script. Use this instead of update_script for managed mobile flows.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
script_id |
integer |
Yes | Managed mobile automation script ID |
flow |
object |
Yes | Complete canonical QTML mobile flow, including its current revision |
Return shape
Section titled “Return shape”The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.
Worked example
Section titled “Worked example”{ "arguments": { "flow": {}, "script_id": 1 }, "tool": "update_mobile_flow"}