Skip to main content
Glama

Visibility Genies

Get link metrics

get_link_metrics

Link metrics of up to 100 domains at once, as the Competitors and Link Prospects pages show them. Ranks and spam scores are 0 to 100 scores, not Google metrics. Estimated price: ~$0.15 for 10 competitors, ~$0.05 for 10 prospects, billed per request and per domain. The same domains saved within 6 hours are read free. 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>",
      "domains": "<domains>"
    },
    "name": "get_link_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNocompetitors (default): domain rank, backlinks, and the backlinks gained and lost in the last 30 days, three requests (the linking sites gained and lost are get_competitor_link_changes'). prospects: domain rank, backlinks, referring domains and spam score, one request.competitors
domainsYes1 to 100 domains.
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
setNo
costNo
metaNo
rowsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 explains why this is not a pure read by disclosing billing: estimates, per-request/per-domain charges, free 6-hour cache, and the spend-limit hold-and-charge behavior. It also explains refusal semantics when the maximum exceeds the workspace limit. What remains undisclosed is latency and failure handling beyond the cost refusal path.

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?

Dense but front-loaded: purpose first, then units caveat, then pricing and the spend-limit/approval flow. Every clause carries billing or mode information the agent needs. It is longer than typical, but the length is justified by a metered tool with an approval loop.

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?

Covers the hard parts of a metered batch tool: pricing, caching, spend caps, and the approval re-call path, and an output schema exists so return values need not be described. Minor gaps remain around validation failures and what happens to partial result sets in the three-request competitors mode.

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 real meaning the schema lacks: per-mode request counts and cost per 10 domains, which drive whether to pick competitors or prospects. The 6-hour free-read behavior also gives context for repeated calls with the same domains.

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 resource and scope: "Link metrics of up to 100 domains at once, as the Competitors and Link Prospects pages show them." That anchors the agent to a known UI view and the batch limit. It stops short of naming a sibling tool (e.g. get_backlinks_overview) as the alternative, so differentiation stays implicit.

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?

Gives clear operational context: two modes (competitors, three requests, vs prospects, one request), per-mode pricing, and a free re-read window for domains saved within 6 hours. The explicit escalation procedure for approvedMaxCostUsd (ask the user, then re-call) is real when-to-use guidance. No exclusions or explicit "use tool X instead" statements are given.

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