Skip to main content
Glama

Crawlgraph Gap Outreach Targets

crawlgraph_gap_outreach_targets
Read-onlyIdempotent

The warm-outreach play: gap_analysis filtered to ONLY the linking domains that link to EVERY competitor you listed but not to you. These are the highest-conviction outreach candidates, every competitor in the set has the link, so the topic/audience is verified. Same async pattern as crawlgraph_gap_analysis (polls up to ~10s; returns job_id if still running). Counts as one gap-analysis quota call.

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",
        "competitor3.com"
      ]
    },
    "name": "crawlgraph_gap_outreach_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesCrawlGraph API key.
my_domainYesYour domain.
min_authorityNoOptional minimum CrawlGraph authority threshold to filter results client-side.
competitor_domainsYes2-5 competitor domains. The filter is strongest with more competitors; 2 is the minimum for "warm outreach" to be meaningful.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / competitor_domains / description
      Previous value: -"2–5 competitor domains. The filter is strongest with more competitors; 2 is the minimum for \"warm outreach\" to be meaningful."New value: +"2-5 competitor domains. The filter is strongest with more competitors; 2 is the minimum for \"warm outreach\" to be meaningful."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the async polling window (~10s), the job_id fallback, and that it consumes one gap-analysis quota call — cost information an agent needs before calling. It does not describe error behavior or what happens when the competitor set yields no intersection.

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 dense sentences, front-loaded with the value proposition, then the mechanics, then the cost. No filler or restatement of the title.

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?

Covers the two things an agent most needs for this complex, async, quota-consuming tool: the execution pattern and the cost. With no output schema, a brief note on what the result rows contain (domains, authority) would close the last 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%, so the schema already documents all four parameters including the 2-5 competitor bound. The description reinforces the filter semantics ('every competitor in the set has the link') but says nothing additional about my_domain or min_authority, 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+resource (linking domains that link to every listed competitor but not to you) and explicitly positions it as 'gap_analysis filtered to ONLY…', which separates it from the sibling gap_analysis tool in one clause.

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?

Frames the use case as 'the warm-outreach play' for 'highest-conviction outreach candidates', naming crawlgraph_gap_analysis as the broader alternative. It implies rather than states the exclusion (use gap_analysis for the full gap set), so it falls just 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.