Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get site audit status

seo_get_audit_status
Read-onlyIdempotent

Shows the progress of a site audit: phase, pages crawled and Lighthouse progress. Free. An audit whose crawl stopped without finishing shows as failed. Omit auditId for the most recent 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": {
      "siteId": "<siteId>"
    },
    "name": "seo_get_audit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
auditIdNoAudit ID. If omitted, uses the project's most recent audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower, yet the description still adds real context beyond them: the audit is free (cost behavior, not encoded anywhere), and a crawl that stopped without finishing reports as failed, which is important interpretive guidance for the returned status. It stops short of describing pagination, latency, or the phase value set.

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

Conciseness4/5

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

Three short sentences, front-loaded with what the tool shows before the cost note and the failure caveat. The final sentence duplicates the auditId default already in the schema, a small amount of waste but nothing bloated.

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?

With no output schema, the description carries the burden of describing return values, and it does name the key fields returned. Given the tool's simplicity (2 params, 1 required, no nesting), what remains missing—the allowed phase values and how to detect completion—is modest rather than a critical hole.

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%, so both siteId and auditId are already documented, including the default-to-most-recent behavior for auditId. The description's closing sentence merely restates that default; the baseline of 3 applies since the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb and resource ("Shows the progress of a site audit") and enumerates the fields returned: phase, pages crawled, Lighthouse progress. That distinguishes it from status-adjacent siblings like seo_list_site_audits or seo_get_audit_issues without naming them explicitly.

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?

The only routing guidance is "Omit auditId for the most recent audit," which is really parameter usage rather than when-to-use-this-tool guidance. It never says to call this after starting an audit, nor points to seo_list_site_audits as the way to obtain an auditId, so the agent must infer the workflow.

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