Skip to main content
Glama

Visibility Genies

Get the backlink gap

get_backlink_gap

Finds link building prospects: the sites that link to up to 4 competitors and not to your domain, each with the competitors it links to (at least, when a competitor has more referring domains than its top rows saved), whether it looks sitewide (more than 50 backlinks to one competitor), the highest rank its links pass (rank passed, a 0 to 100 link-graph score, not a Google metric, which sitewide links inflate), its average link spam and its backlinks to them. Estimated price: up to $0.12 for each competitor, one backlinks request for its top 1,000 referring domains by rank, billed by the rows returned. A competitor saved for this domain within 6 hours is read free, and the gap opens free on the Backlink Gap page; get_saved_backlink_gap reads it without buying. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "competitors": "<competitors>"
    },
    "name": "get_backlink_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many referring domains to return, best prospects first: those linking to the most competitors, then the strongest, with those whose average link spam is above 60 (the high band) last. Defaults to 100.
domainNoYour domain. Defaults to the project's own.
offsetNoHow many of the best prospects to skip, to read further on.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsYes1 to 4 competitor domains, e.g. ['example.org'].
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
rowsNo
savedNo
domainNo
competitorsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=false, openWorldHint=true, and destructiveHint=false; the description adds far more context. It explains the pricing model (up to $0.12 per competitor, billed by rows returned), the spend-limit behavior (a hold of estimate plus margin, charged what was bought and never more, refused before purchase if over the limit), a 6-hour free cache, and how it detects sitewide links and computes rank passed (a 0-100 link-graph score, not a Google metric).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose is front-loaded well, but the body is a single sprawling passage with stacked parentheticals, which makes the billing and ranking semantics hard to parse. The pricing and spend-limit details are essential, yet the same cost policy is restated multiple times (estimate, maximum, hold, charged, refusal), so some trimming would help.

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?

For a billed, open-world tool with six parameters and an output schema, the description covers what an agent needs. It explains cost, the spend limit, the refusal and approval path, the free cached alternative, and the meaning of the derived metrics, while the output schema covers the return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not. It explains that rank passed is a link-graph score rather than a Google metric and that sitewide links inflate it, and it gives the full approval workflow for approvedMaxCostUsd: set it only after a refusal, and only with user approval.

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?

The description uses a specific verb and resource: 'Finds link building prospects: the sites that link to up to 4 competitors and not to your domain.' It states the scope clearly, including up to 4 competitors, and names the sibling get_saved_backlink_gap as the free read path, so an agent can distinguish the two without opening either schema.

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?

The description gives useful routing context by noting that the gap opens free on the Backlink Gap page and that get_saved_backlink_gap reads it read-free, and it explains the cost-refusal path: ask the user, then retry with approvedMaxCostUsd. It never explicitly says 'use this tool when you need fresh competitor gap data rather than saved data', so the selection rule remains partly inferential.

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.

Resources