Skip to main content
Glama

Visibility Genies

Get a backlinks overview

get_backlinks_overview

Returns a backlinks profile summary (total backlinks, referring domains, domain rank, spam scores, 12 months of trends) and the top referring domains, each with the rank its links pass to the target (sitewide links inflate it). Ranks and spam scores are 0 to 100 scores, not Google metrics. Estimated price: ~$0.16 for a domain (three Backlinks API calls: totals, 12 months of trends, 100 referring domains), ~$0.10 without the referring domains, ~$0.11 for a single page. These are the Backlinks page's own purchases: what is bought here opens free there, and what it holds is answered here at no charge while it is current. Bare domains default to scope 'subdomains'; pass scope 'domain' to exclude subdomains from the totals. Targets with a path default to 'subfolder', whose counts come from filtered backlink totals (no rank, trends or referring-domain breakdown). Trend data always includes subdomains (provider limitation). 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>"
    },
    "name": "get_backlinks_overview"
  }
}

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.
targetYesDomain or URL to analyze (e.g. 'example.com' or 'https://example.com/blog').
hideSpamNoLeave out referring domains whose links' average spam score is above 60, its high band. A spam score is an estimate, not Google's. Defaults to false, as the Backlinks page does, so the domains bought here open free there.
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.
includeReferringDomainsNoAlso buy the 100 referring domains with the most backlinks. Defaults to true; subfolders have no breakdown.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
scopeYes
targetYes
overviewYes
scopeNoteNo
savedResultIdNo
referringDomainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The annotations only declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description carries the real behavioral load. It discloses that calls purchase data against a metered balance, that the workspace agent spend limit ($2.00 default) gates each call, that over-limit calls are refused before anything is bought, and that holdings are cross-honored with the Backlinks page. It even flags a provider limitation (trends always include subdomains) and defines the 0-100 rank and spam scales as non-Google estimates.

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?

For a metered, six-parameter tool the length is proportionate: it front-loads what is returned, then cost, then defaults, then the spend-limit escape hatch. Sentences are dense but each carries a distinct operational fact and there is no filler.

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?

An output schema exists, so return values needn't be spelled out, and cost, billing, defaults and refusal handling are all covered — unusually complete for a purchase-incurring tool. The remaining gap is selection: nothing tells the agent how this differs from the sibling backlinks tools, and no auth requirement beyond the projectId pointer is stated.

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, and the description earns more by adding meaning the schema lacks: bare domains default to 'subdomains' while paths default to 'subfolder', and subfolder counts omit rank, trends and the referring-domain breakdown. It also explains why hideSpam defaults to false. Some of this repeats the scope parameter's own description rather than adding to it, which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource and enumerates the payload: totals, referring domains, domain rank, spam scores, 12 months of trends, and the top referring domains with pass-through rank. That is far beyond a restated name. It falls short of a 5 because it never distinguishes itself from siblings like get_backlinks_profile or get_backlinks_report, so an agent cannot route between the backlinks tools on this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Useful conditional guidance is present in the pricing tiers (~$0.10 without referring domains, ~$0.11 for a single page) and in the explicit refusal-then-retry procedure with approvedMaxCostUsd. However, there is no statement of when to prefer this tool over the sibling backlinks/profile tools, and no explicit 'not for X' exclusion. Usage must be inferred from cost variants rather than stated as task fit.

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