Skip to main content
Glama

Crawlgraph Gap Analysis

crawlgraph_gap_analysis
Read-onlyIdempotent

Backlink gap analysis: find domains linking to your competitors but NOT to you. Submit your domain + 1-5 competitor domains and CrawlGraph runs an async job (typically completes in seconds; longer for large profiles). This tool polls up to ~10s and either returns the full gap list, or, if still running, returns the job_id so you can resume via crawlgraph_gap_status. Counts against the gap-analysis quota when the job is submitted.

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": {
      "_apiKey": "your-crawlgraph-api-key",
      "my_domain": "mysite.com",
      "competitor_domains": [
        "competitor1.com",
        "competitor2.com"
      ]
    },
    "name": "crawlgraph_gap_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesCrawlGraph API key.
my_domainYesYour domain (bare host).
competitor_domainsYes1-5 competitor domains to compare against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / competitor_domains / description
      Previous value: -"1–5 competitor domains to compare against."New value: +"1-5 competitor domains to compare against."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld, but the description adds genuinely non-obvious behavior: the job is async, polling runs up to ~10s, and on timeout a job_id is returned for resumption. It also discloses that the call consumes gap-analysis quota on submission — a real side effect an agent would otherwise miss.

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 value proposition, then mechanics, then the fallback path. The parenthetical about runtime for large profiles is short and earns its place by setting timing expectations.

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?

No output schema exists, so the description carries the return-value burden — and it does, describing both outcomes (full gap list vs. job_id). Combined with quota and async disclosure, an agent has everything needed to call it and handle the result.

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 minItems/maxItems already encoding the 1-5 competitor bound and per-field descriptions covering bare-host format and the API key. The description restates the competitor count without adding format or validation detail beyond the schema, so baseline 3 applies.

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 and resource with precise scope: 'find domains linking to your competitors but NOT to you.' The negative-set framing distinguishes it clearly from crawlgraph_backlinks (your own links) and from crawlgraph_gap_status (resume an existing job).

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?

Gives concrete input requirements (your domain + 1-5 competitors) and explicitly routes to crawlgraph_gap_status when the job is still running. It does not contrast with crawlgraph_gap_outreach_targets, which an agent might also consider for follow-up action, so it stops just short of full alternative coverage.

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.