Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get site audit issues

seo_get_audit_issues
Read-onlyIdempotent

Read the prioritized issue report from a completed site audit. Every issue carries a how_to_fix with concrete remediation steps an agent can act on. Free — reads Sextant state. Omit auditId for the newest finished audit (the newest audit when none has finished); audit says which one was read.

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_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax issues to return (default 200).
siteIdYesThe Sextant site ID.
auditIdNoAudit ID. If omitted, uses the project's most recent audit.
severityNoOnly return issues of this severity.
issueTypeNoOnly return issues of this type. One of: blocked-page, javascript-rendering-suspected, rate-limited-page, crawl-rate-limited, server-error, broken-internal-link, missing-title, broken-page, duplicate-title, duplicate-meta-description, duplicate-content, missing-meta-description, missing-h1, multiple-h1, redirect-chain, redirect-loop, canonical-conflict, thin-content, images-missing-alt, orphan-page, no-outgoing-links, title-too-long, title-too-short, meta-description-too-long, meta-description-too-short, heading-order-skip, slow-response, noindex-page, canonicalized-page, home-missing-structured-data, structured-data-invalid, deep-page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real value beyond them: it is free (no credit cost), it reads Sextant state, it discloses that every issue carries a how_to_fix with concrete remediation steps, and it describes the fallback resolution of auditId plus the 'audit' field reporting which audit was read. It says nothing about result truncation at the limit.

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?

Four short sentences, front-loaded with the core purpose, with no filler; each sentence contributes either routing, cost, return-content or default-behavior information. The em-dash asides make it slightly dense to parse but nothing is redundant.

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 5-parameter read tool with full schema coverage, annotations and no output schema, the description covers cost, precondition, default audit selection and the shape of returned issues. The remaining gap is that it never mentions the 1-1000 limit range or that results may be truncated, which matters for an agent deciding whether one call is enough.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented and the baseline is 3. The description nevertheless adds meaning beyond the schema by sharpening auditId omission into 'newest finished audit (the newest audit when none has finished)', which resolves the ambiguity the schema's 'most recent audit' leaves. limit, severity and issueType receive no description-side elaboration.

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 ('Read the prioritized issue report from a completed site audit'), and 'prioritized issue report' distinguishes it from sibling tools like seo_get_audit_pages or seo_get_audit_status. It stops short of naming any sibling explicitly, so an agent must infer the routing from the noun alone.

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

Usage Guidelines4/5

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

'from a completed site audit' tells the agent the precondition, and 'Omit auditId for the newest finished audit' gives a clear actionable rule for the common case. It does not explicitly say to check seo_get_audit_status first when no audit has finished, nor does it state any exclusion relative to the page-level report sibling.

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