Skip to main content
Glama

Visibility Genies

Read audit status

get_audit_status

Shows how a site audit is going: its phase, pages crawled and Lighthouse progress, which crawler identity it used (crawlerIdentity), its pace (fasterCrawl is true only for the Owner's faster crawl of their own server; otherwise about a page a second), the addresses the crawler sends from (crawlerAddresses), whether it rendered pages with JavaScript (renderJavaScript; a page that could not be rendered was read as plain HTML) and whether the Owner's setting let it ignore robots.txt (robotsTxtIgnored). A finished audit also reports its Site health and AI readiness scores out of 100, matching Site Audit. Free: it reads Visibility Genies data, and it may mark an audit failed when its workflow has died. Leave out auditId for the latest audit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_audit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditIdNoAudit ID. Leave it out to use the project's latest audit.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: it explains why a nominally read-shaped call has readOnlyHint=false by disclosing 'it may mark an audit failed when its workflow has died,' plus cost ('Free: it reads Visibility Genies data') and the crawler semantics (fasterCrawl scope, robotsTxtIgnored, renderJavaScript fallback to plain HTML). What remains unstated is cadence/pagination advice for polling a long-running audit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body is a single ~130-word sentence stitched together with parentheticals that is hard to parse at a glance. Several clauses explain output fields that an output schema already defines, so some of the bulk does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter status read with an output schema, the description covers purpose, the surprising failure-marking side effect, cost, and the meaning of non-obvious fields. Only polling behavior and routing relative to sibling audit tools are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description's only parameter guidance ('Leave out auditId for the latest audit') largely restates the auditId schema text. It says nothing about projectId beyond what the schema already documents, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Shows how a site audit is going: its phase, pages crawled and Lighthouse progress') and enumerates the exact facets reported, so an agent can distinguish it from get_audit_issues, get_audit_pages and run_site_audit without opening any schema. The scope is a status/progress read on an existing audit, stated unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (poll this while an audit runs) and the only explicit routing instruction is 'Leave out auditId for the latest audit,' which is a parameter rule rather than a when-to-use rule. It never says when to prefer this over get_audit_issues/get_audit_pages, nor any exclusion or prerequisite beyond the required projectId.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources