Skip to main content
Glama

get_site_audit_history

Read-only

A client's SEO audit crawls over time, oldest first: per crawl its date, status, pages requested, Site Health and AI Search Health with n, site-wide errors, new / fixed against the previous comparable crawl, and whether it has the latest crawl's scope (only those compare), plus the key-page monitor's newest changes.

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": "get_site_audit_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCrawls returned, default 12.
clientIdYesClient id (from list_clients).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and closed-world, so safety is covered. The description adds real value beyond that: oldest-first ordering, the 'comparable crawl' rule governing new/fixed counts, and the inclusion of key-page monitor changes. It still says nothing about truncation when limit is hit or the result envelope.

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

Conciseness2/5

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

The content arrives as one dense ~50-word run-on sentence with a colon and a parenthetical, and it leads with return-field enumeration instead of the tool's function. Nothing is front-loaded and the field lists are hard to parse on a single read.

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

Completeness3/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 does correctly shoulder the burden of describing return fields (dates, status, page counts, Site Health/AI Search Health with n, errors, new/fixed, scope flag, key-page changes). However, it omits limit/truncation behavior and any hint of response shape, leaving gaps for a history-retrieval tool.

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%, with both clientId and limit documented including the default of 12 and max of 24. The description mentions date ordering but never references the limit parameter or what happens when the history exceeds it, so it adds nothing the schema doesn't already carry.

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

Purpose3/5

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

The description conveys the resource (a client's SEO audit crawl history, ordered oldest first) but is phrased as a list of returned fields rather than a verb+resource statement of what the tool does. It gives no differentiation from close siblings like get_site_audit or compare_site_audits, which an agent could easily confuse it with.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this versus get_site_audit (current crawl) or compare_site_audits (pairwise comparison). The only indirect cue is 'only those compare', which hints at a comparability rule but never routes the agent to an alternative.

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