Skip to main content
Glama

Black SEO Analyzer

compare_crawls

Read-only

Compare two crawls of the same site and report which issues are new in the later crawl, which were fixed, and how many persist. Use it to answer "did my changes help?" or "what regressed since the last deploy?", and to gate a release: only the new_issues list represents a regression, so a pre-existing backlog never counts against a change. Get both session ids from list_crawls; base_session is the earlier crawl.

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": {
      "base_session": "<base_session>",
      "compare_session": "<compare_session>"
    },
    "name": "compare_crawls"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_sessionYesSession id of the earlier ("before") crawl.
compare_sessionYesSession id of the later ("after") crawl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by explaining the semantics of the result (only new_issues is a regression, pre-existing backlog is excluded) which is behavior an agent cannot infer from annotations. It does not mention failure modes such as comparing crawls of different sites or non-comparable sessions, which keeps it from a 5.

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 sentences, front-loaded with the operation and its result categories before the use cases and the parameter hint. No filler, and the release-gating rule is stated as a single crisp constraint.

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?

There is no output schema, so the description carries the burden of describing return values and does so by naming new_issues, fixed issues, and the persist count. For a two-parameter read-only comparison tool with full schema coverage, nothing an agent needs to invoke it correctly is missing.

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% and the schema already labels base_session as the earlier crawl and compare_session as the later one, so the description's closing note largely restates structured data. The added value is limited to pointing at list_crawls as the id source, which is a workflow hint rather than parameter semantics.

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 (compare) and resource (two crawls of the same site), then immediately enumerates the output categories: new issues, fixed issues, and persisting count. That distinguishes it from sibling tools like list_crawls or query_issues without needing the schema.

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

Usage Guidelines5/5

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

Gives concrete triggering questions ("did my changes help?", "what regressed since the last deploy?") and a specific workflow (release gating where only new_issues counts as a regression). It also points to list_crawls as the source of session ids, so the agent knows the prerequisite step.

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.