Skip to main content
Glama

Compare site audit snapshots

compare_site_audits
Read-onlyIdempotent

Compare the structured results of two earlier audit_public_site runs entirely offline. Identify changed page issue counts, unavailable checks, sitemap drift, and newly/no-longer observed grouped findings only within the same fully checked selected-page sample (not site-wide). This is not a Google indexing, ranking, or traffic-causality test. No webpages are fetched and results are not stored.

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": {
      "baseline": "<baseline>",
      "current": "<current>"
    },
    "name": "compare_site_audits"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentYesLater structuredContent from audit_public_site, ideally the same sitemap batch.
baselineYesEarlier structuredContent from audit_public_site, without editing its page list.

Output Schema

NameRequiredDescriptionDefault
statusYes
overviewYes
limitationsYes
mixed_pagesYes
page_changesYes
improved_pagesYes
pages_comparedYes
regressed_pagesYes
current_site_urlYes
baseline_site_urlYes
coverage_lost_pagesYes
newly_selected_urlsYes
current_selected_pagesYes
expanding_issue_groupsYes
shrinking_issue_groupsYes
baseline_selected_pagesYes
no_longer_selected_urlsYes
coverage_recovered_pagesYes
newly_observed_issue_groupsYes
no_longer_observed_issue_groupsYes
issue_group_comparison_availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: entirely offline, no webpages fetched, results not stored, and comparison confined to the selected-page sample. It stops short of saying how mismatched samples are handled (error vs. partial comparison), which is the remaining behavioral gap.

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 front-loaded sentences with no filler: the operation, the specific deltas detected, and the negative scope disclaimers. Every sentence contributes something an agent cannot get from the schema or annotations.

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 tool consuming two large nested audit payloads, the description covers data provenance, offline behavior, non-persistence, and the sampling caveat, and an output schema exists so return values need no explanation. The only missing piece is failure behavior when the two inputs are not comparable.

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 description coverage is 100%, with both baseline and current documented as earlier/later structuredContent from audit_public_site, so the schema already carries the parameter meaning and baseline 3 applies. The description adds only a light constraint that the two must belong to the same fully checked sample, which is useful but not detailed enough to elevate beyond 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 ('Compare the structured results of two earlier audit_public_site runs') and immediately bounds the scope to the same fully checked selected-page sample rather than site-wide. It also pins the data source to a named sibling, so the agent knows exactly which tool produces the inputs.

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?

Clear context for use: two prior audit_public_site runs, baseline (earlier) and current (later). It adds explicit when-not guidance by ruling out indexing, ranking, and traffic-causality interpretations. It does not state what to do if the two snapshots come from different sites or discovery fingerprints, but the core use condition is unambiguous.

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