Skip to main content
Glama

Visibility Genies

Get a backlinks report

get_backlinks_report

Buys one Backlinks report for a domain or page: best_pages (up to 100 of a domain's pages with the most linking sites, with titles) or referring_networks (up to 100 IP addresses or subnets its links come from). Estimated price: up to ~$0.06 a report, one backlinks request billed by the rows returned. A report saved within 6 hours is read free, and it opens free on the Backlinks page's tab of the same name. For the sites whose links overlap a domain's, use find_link_competitors. 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>",
      "target": "<target>",
      "report": "<report>"
    },
    "name": "get_backlinks_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoWhich part of the site to research. One of: exact_url (a single page), subfolder (the path and everything under it), domain (the hostname without subdomains), subdomains (the hostname plus all of its subdomains). Defaults to subdomains for a bare domain and to subfolder when the input includes a path. The earlier name "page" is deprecated; it is read as exact_url. Subfolder counts are derived from filtered backlink totals, so rank, trends and the referring domains breakdown are unavailable for a subfolder.
reportYesbest_pages: the target's pages with the most linking sites (a whole domain only). referring_networks: the IP addresses or subnets its links come from.
targetYesDomain or URL, e.g. 'example.com'.
networkNoreferring_networks only: subnet (default) or ip.subnet
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
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
reportNo
targetNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description supplies the whole economics layer: estimated ~$0.06, billing by rows returned, a 6-hour free re-read, the workspace agent spend limit ($2.00 default), a temporary hold of estimate plus margin, charge-never-more-than-bought, and pre-purchase refusal above the limit. That is exactly the extra context annotations cannot carry.

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?

Front-loaded with purpose and the report variants before cost mechanics, and every cost sentence is load-bearing for a tool that spends money. It is dense and run-on in places (multiple spend-limit clauses in one paragraph), so slightly tighter grouping would help, but nothing is redundant.

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?

Given an output schema and 100% schema coverage, the description only needs to cover cost, caching and escalation behavior — and it does all three, plus the sibling alternative. Nothing an agent needs before calling is missing.

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 schema already defines scope, report, network, projectId and approvedMaxCostUsd. The description still adds non-schema meaning: the 100-item caps per report type and the billing-per-row consequence of the chosen report, plus the framing of approvedMaxCostUsd as user-approved post-estimate. Marginal but real value above baseline 3.

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?

Opens with a specific verb and resource ("Buys one Backlinks report for a domain or page") and then defines the two report variants with their concrete contents (up to 100 pages with titles; up to 100 IPs/subnets). An agent immediately knows this is a paid, single-report fetch, which distinguishes it from sibling report/overview tools.

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 agent away when appropriate: "For the sites whose links overlap a domain's, use find_link_competitors." It also gives a precise escalation procedure for spend-limit refusals (ask the user, then retry with approvedMaxCostUsd set to the approved amount), which is the main when/how guidance an agent needs here.

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