Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

compare_site_audit_crawls

Compares two site audit crawls to show what regressed or improved since the last one, returning health score changes plus new, resolved, worsened and improved issues with page counts and deltas.

Instructions

Diff two crawls to answer "what regressed or improved since last time?" — health_diff plus counts and four lists: new_issues, resolved_issues, worsened and improved, each issue carrying pages_affected, prev and delta. Defaults to the latest crawl vs the previous one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_site_audit_crawls"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load: it discloses the output shape (health_diff, counts, four named lists with pages_affected/prev/delta) and the default selection behavior, which is genuinely useful. However, it never states that this is a read-only operation, nor how an agent would override the default and pick two specific crawls, leaving a real behavioral gap for a zero-parameter schema.

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?

The purpose is front-loaded in the first clause, followed by the return structure and then the default behavior — a logical progression with no filler sentences.

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?

There is no output schema, and the description compensates well by enumerating the returned fields and lists. The remaining gap is how to target a non-default pair of crawls, which matters given an empty input schema with additionalProperties allowed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool declares zero parameters, so the baseline is 4. The description adds relevant meaning by explaining the default operand selection (latest vs previous crawl), which is exactly the semantics an agent needs in the absence of declared parameters.

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 description states a specific verb and resource ("Diff two crawls") and frames the question it answers, which differentiates it from the sibling listing tools like list_site_audit_issues or get_site_audit_summary that report a single crawl rather than a comparison.

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?

It gives clear situational context ("what regressed or improved since last time?") and states the default comparison (latest crawl vs the previous one), which tells an agent when this tool fits. It does not name an alternative or state exclusions, so it falls short of explicit when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools