Skip to main content
Glama

list_site_audit_pages

Read-only

The URLs of a client's SEO audit crawl, highest priority first, then most Google clicks: state, HTTP status, indexable and why not, click depth, internal links in, title, words, issues, value tier, priority, Google clicks / impressions (28 days), AI answers citing the page, tracked keywords ranking, AI-crawler fetches (30 days) and how the URL was found. A query variant of another crawled page, or a page canonicalised to another URL of the same page, has null value figures and valueCountedOn names that URL: the figures are counted there, never repeated here. Filters: state, valueTier, issueId, urlContains, httpStatus, indexable, depth, source. total counts every matching URL; rows are paged (offset).

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": {
      "clientId": "<clientId>"
    },
    "name": "list_site_audit_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoOnly pages at this click depth from the start page.
limitNoRows returned, default 50.
stateNoOnly this crawl state (blocked = closed by robots.txt, refused = refused our crawler).
offsetNoSkip this many rows (paging).
sourceNoOnly URLs found this way.
crawlIdNoA finished crawl. Default: the latest that ran to the end.
issueIdNoOnly pages with this issue.
clientIdYesClient id (from list_clients).
indexableNoOnly indexable (true) or non-indexable (false) pages.
valueTierNoOnly this value tier (1 = key page; none = not tiered).
httpStatusNoOnly this HTTP status.
urlContainsNoOnly URLs containing this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnly/openWorld annotations, it discloses non-obvious semantics: query-variant and canonicalised pages carry null value figures with valueCountedOn pointing at the counted URL, so figures are 'never repeated here', and total counts every matching URL while rows are paged by offset. That is the aggregation behavior an agent would otherwise get wrong.

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?

Two dense sentences with the resource and ordering front-loaded; the long column enumeration is justified because no output schema exists, though the run-on structure makes it heavier to parse than necessary.

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

Completeness5/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 return shape itself — column list, ordering, null-value caveat, and paging/total contract — which is everything an agent needs to call and interpret this 12-parameter list tool correctly.

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 each of the 12 parameters is already documented in the schema; the description only restates the filter list and adds no syntax or format detail beyond it. Baseline 3 is appropriate given the schema does the per-parameter work.

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?

The first clause names the exact resource ('The URLs of a client's SEO audit crawl') and the ordering ('highest priority first, then most Google clicks'), which lets an agent distinguish this bulk row-listing from the single-page sibling get_site_audit_page and the issue-level sibling list_site_audit_issues.

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 by the enumeration of filters ('Filters: state, valueTier, issueId, ...') and by the note about paging, but it never states when to prefer this over get_site_audit_page, get_crawl_insights, or list_site_audit_issues, nor any prerequisites beyond the crawlId default.

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