crawlgraph_domain_changes
Pack: crawlgraph · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/crawlgraph_domain_changes for the schema, then POST the same URL with its arguments for the data.
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Target domain. |
from | string | no | Older release_id (e.g., “CC-MAIN-2025-51”). Default = previous release. |
to | string | no | Newer release_id (e.g., “CC-MAIN-2026-04”). Default = latest release. |
_apiKey | string | yes | CrawlGraph API key. |
Example call
Arguments
{
"domain": "example.com",
"_apiKey": "your-crawlgraph-api-key"
}
curl
curl -X POST https://gateway.pipeworx.io/crawlgraph/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"crawlgraph_domain_changes","arguments":{"domain":"example.com","_apiKey":"your-crawlgraph-api-key"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('crawlgraph_domain_changes', {
"domain": "example.com",
"_apiKey": "your-crawlgraph-api-key"
});
More examples
{
"domain": "example.com",
"from": "CC-MAIN-2025-51",
"to": "CC-MAIN-2026-04",
"_apiKey": "your-crawlgraph-api-key"
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the crawlgraph pack
{
"mcpServers": {
"crawlgraph": {
"url": "https://gateway.pipeworx.io/crawlgraph/mcp"
}
}
}
See Getting Started for client-specific install steps.