Skip to main content
Glama

Crawlgraph Domain Changes

crawlgraph_domain_changes
Read-onlyIdempotent

Quarter-over-quarter diff of referring domains for a domain, what was added or lost between two Common Crawl releases. Useful for catching link rot, sudden spikes (PR coverage), and outreach campaign attribution. Counts as one call against the backlinks quota.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "example.com",
      "_apiKey": "your-crawlgraph-api-key"
    },
    "name": "crawlgraph_domain_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoNewer release_id (e.g., "CC-MAIN-2026-04"). Default = latest release.
fromNoOlder release_id (e.g., "CC-MAIN-2025-51"). Default = previous release.
domainYesTarget domain.
_apiKeyYesCrawlGraph API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine behavioral value beyond them: the quota cost ('counts as one call against the backlinks quota') and the shape of what is returned (added vs lost referring domains). It does not disclose result-size limits or ordering, so it falls short of 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 tight sentences: what it does first, why you would use it second, cost caveat last. No filler, and the quota note earns its place because it affects calling behavior.

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 four-parameter, fully documented, read-only diff tool with no output schema, the description is nearly sufficient: operation, motivation, and cost are all present. A brief note on what the returned diff looks like (counts vs domain lists) would close the remaining gap.

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 per-parameter descriptions and examples, so the baseline is 3. The description adds only the idea that from/to are Common Crawl releases being diffed, which the schema already conveys via release_id descriptions and defaults; no extra semantics about ordering, directionality of the diff, or release-id validation are supplied.

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

Purpose4/5

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

States a specific operation on a specific resource: a quarter-over-quarter diff of referring domains between two Common Crawl releases, with added/lost framing. It is far from tautological, but it never names a sibling (e.g. recent_changes or crawlgraph_backlinks) that an agent might confuse it with, so differentiation is left implicit.

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?

It lists motivating use cases (link rot, spike detection, outreach attribution), which implies when the tool is appropriate. However, there are no explicit when-not conditions, no comparison to the adjacent recent_changes or backlinks tools, and no guidance on default vs explicit release selection.

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.