Skip to main content
Glama

Visibility Genies

Get a backlinks profile

get_backlinks_profile

Returns one page of backlink rows for a domain or URL, with filters, sorting, a mode and paging. Every link is live; lost links are not bought. Estimated price: ~$0.06 for 50 rows, ~$0.07 for 200, billed by the rows returned. It is the Backlinks page's own table: a page bought here opens free there and the other way round, while its saved copy is current. 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoone_per_domain (default) returns the strongest link of each linking domain; as_is returns every backlink row.one_per_domain
pageNo
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 whose backlinks to list.
filtersNoNarrow the rows: source URL terms to include or exclude, domain rank and link rank ranges, link spam, dofollow or nofollow, hide broken links, or an exact linking domain.
hideSpamNoLeave out rows whose spam score is above 60. Defaults to false.
pageSizeNoRows per page: 50, 100, 200.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
sortFieldNofirstSeen
sortOrderNodesc
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
scopeYes
targetYes
backlinksYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With readOnlyHint=false and openWorldHint=true already signalling a billable external call, the description goes well beyond them: exact row pricing (~$0.06/50 rows, ~$0.07/200), that charges are capped at the workspace agent spend limit, that budget is held during the run, that over-limit calls are refused before anything is bought and returned with an estimate plus maximum, and the exact recovery step (ask the user, retry with approvedMaxCostUsd). It also discloses that only live links are billable and that pages are shared/cached with the Backlinks UI.

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?

Purpose is front-loaded in the first sentence and cost rules follow in a logical order. The billing/spend-limit block is dense and slightly repetitive (estimate, hold, charged, refused all restated), but nearly every clause carries decision-relevant information for an agent that can spend money.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Strong on cost and approval behavior, and the output schema covers return shape. However, for an 11-parameter tool with nested filters, four enums and a subfolder caveat in the schema, the description gives no guidance on scope/mode selection or filter usage, and never indicates which sibling tool to reach for instead.

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 73%, so most parameters are already documented. The description still adds meaning the schema cannot: pageSize values map to concrete prices, and approvedMaxCostUsd gains an operational rule (only set after a refusal and only with user approval) that explains when and why to populate it.

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?

States a specific verb and resource: 'Returns one page of backlink rows for a domain or URL, with filters, sorting, a mode and paging.' That is concrete enough to separate it from higher-level siblings like get_backlinks_overview or get_backlinks_report, but the description never names an alternative, so the distinction must be inferred from 'page of rows' phrasing.

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?

Usage context is implied rather than stated: it is the raw per-page table behind the Backlinks page, and the mode enum hints at one-per-domain versus all-rows use. There is no explicit 'use this instead of X when Y' guidance and no stated prerequisites for choosing this over the sibling overview/report tools.

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