Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get site audit pages

seo_get_audit_pages
Read-onlyIdempotent

List crawled pages from a site audit with per-page SEO data (status, title, description, word count, indexability, crawl depth, link counts). 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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax pages to return (default 100).
siteIdYesThe Sextant site ID.
auditIdNoAudit ID. If omitted, uses the project's most recent audit.
fetchClassNoFilter by fetch outcome ("blocked" = the site's bot protection challenged the crawler; "rate_limited" = a 429 prevented the crawler from reading the page).
statusCodeNoFilter by exact HTTP status code.
urlContainsNoFilter to URLs containing this substring.

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 cover read-only, idempotent, non-destructive and closed-world, so the safety profile is known. The description still earns credit by disclosing cost ('Free — reads Sextant state') and the non-obvious audit-resolution fallback, plus the fact that the response tells you which audit was actually read.

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

Conciseness5/5

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

Three dense sentences: what is returned with its field list, then cost, then the auditId rule. Nothing is padded and the most load-bearing information leads.

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, listing the returned per-page fields is exactly what the description owes the agent, and the audit-selection caveat closes the main ambiguity. It does not discuss result ordering or pagination beyond the schema's limit parameter, which is a minor gap for a listing endpoint.

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 every parameter, including the fetchClass enum meanings, is documented in the schema. The description only adds nuance to the auditId default, which the schema already summarizes, so this sits at the baseline.

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?

States a specific verb and resource ('List crawled pages from a site audit') and enumerates the per-page SEO fields returned, which cleanly separates it from seo_get_audit_issues and seo_get_audit_status, whose names imply issue-level and run-level data rather than page-level rows.

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?

Gives useful trigger guidance for the auditId default (omit it for the newest finished audit, falling back to the newest audit when none has finished), but says nothing about when to prefer this over seo_get_audit_issues or seo_inspect_urls, and no exclusions are stated.

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