Skip to main content
Glama

Visibility Genies

Get the backlink gap by page

get_backlink_gap_pages

Finds link building prospects page by page: up to 500 referring pages that link to every competitor named and not to your domain, strongest link first, with each page's title, domain rank, link spam and its anchor to each competitor. Use get_backlink_gap for the sites instead. Estimated price: up to $0.09 for one competitor, up to ~$0.20 for 4, one backlinks request billed by the rows returned. The same set saved within 6 hours is read free, and it opens free on the Backlink Gap page, By page. 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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoYour domain. Defaults to the project's own.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsYes1 to 4 competitor domains. Each page returned links to every one of them.
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
domainNo
competitorsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description supplies the costly behavior the agent actually needs — billed by rows returned, per-call estimate ($0.09 to ~$0.20), $2.00 default spend ceiling, hold-plus-margin charging, and the pre-authorization refusal flow. That is material behavior no structured field conveys.

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?

Front-loads the concrete deliverable in the first sentence, then alternatives, then cost and spend-limit mechanics — each sentence carries distinct operational information despite the length. The cost sentence is dense but not padded.

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 paid, open-world, write-gated-by-cost tool with an output schema and full parameter coverage, the description covers everything an agent needs to call it correctly: cost, caching, spend limits, refusal handling and the sibling alternative.

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 projectId, competitors, domain and approvedMaxCostUsd are already documented, and the description largely restates the cost/approval semantics the schema itself states. It adds no format or syntax detail beyond the schema, so the 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?

Names a specific verb ('Finds link building prospects') plus the exact resource granularity (referring pages), the row cap (up to 500), the inclusion rule (links to every competitor named and not to your domain), the ordering (strongest link first) and the returned fields. It also explicitly distinguishes itself from get_backlink_gap ('for the sites instead'), so an agent can choose between them 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the page-level vs site-level use case to the sibling get_backlink_gap, and describes the escalation path when a call exceeds the workspace spend limit: refuse, ask the user, then retry with approvedMaxCostUsd. It also states when results are free (a set saved within 6 hours, or viewing on the Backlink Gap page), which is genuine when-to-use 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.

Resources