Skip to main content
Glama

Crawlgraph Backlinks

crawlgraph_backlinks
Read-onlyIdempotent

Referring domains for a target domain from the Common Crawl webgraph (4.4B edges, 120M domains). Returns linking domains ranked by CrawlGraph authority, useful for SEO audits, competitor backlink profiles, link-building gap research, and verifying who is citing a brand. One call = one quota credit.

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_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by "authority" (default) or "hosts" (number of distinct linking hosts).
limitNoMax linking domains to return (default 1000, max 10000).
domainYesTarget domain to look up (e.g., "example.com"). Bare host, no scheme.
_apiKeyYesCrawlGraph API key (cg_live_... Bearer token).
release_idNoOptional Common Crawl release (e.g., "CC-MAIN-2026-04"). Default = latest. Use crawlgraph_releases to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"CrawlGraph API key (cg_live_… Bearer token)."New value: +"CrawlGraph API key (cg_live_... Bearer token)."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description's job is additive and it delivers: dataset scale (4.4B edges, 120M domains), authority-based ranking, and an explicit quota cost ('one call = one quota credit') that annotations cannot express. It does not describe pagination or response fields, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what is returned and from where, followed by use cases and the cost note. The use-case enumeration is slightly padded but each item is meaningfully distinct rather than filler.

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?

With no output schema, the description carries the return-value burden and does so at a summary level ('linking domains ranked by CrawlGraph authority'), plus it flags the quota cost and points at crawlgraph_releases implicitly through the schema. The absence of response-field detail (e.g., per-domain authority values, host counts) is the main 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 description coverage is 100%, so sort enums, limit bounds, bare-host domain format, and release_id are already fully documented in the schema. The description reinforces authority ranking but adds no syntax or constraint detail beyond that, making the baseline 3 appropriate.

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?

The description names a specific resource ('referring domains for a target domain') and the underlying data source (Common Crawl webgraph), so an agent can tell this is a backlink lookup rather than a change feed or gap analysis. It stops short of explicitly contrasting itself with siblings such as crawlgraph_gap_analysis, which also touches link-gap research.

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?

Usage context is stated concretely: SEO audits, competitor backlink profiles, link-building gap research, and brand citation verification. However, no exclusions or alternative-selection rules are given, so an agent deciding between this and crawlgraph_gap_analysis must infer the boundary from the use-case list.

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.