Skip to main content
Glama

Visibility Genies

Get competitor link changes

get_competitor_link_changes

Counts the linking sites the project and each tracked competitor gained and lost in the last 30 days, all in one request. Estimated price: up to up to $0.06, one backlinks request plus a row per site. A count saved within a day that holds every site asked is 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>"
    },
    "name": "get_competitor_link_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitesNoThe sites to count. Defaults to the project's own and every tracked competitor.
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
boughtNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare openWorldHint=true and destructiveHint=false; the description goes much further by disclosing pricing (up to $0.06), the per-site cost model, free same-day cached reads, the workspace agent spend limit, that the hold is at most estimate plus margin and billing never exceeds the purchase, and exactly what happens when a call is refused. It also explains the recovery path (ask the user, retry with approvedMaxCostUsd). This is behavior an agent could not infer from annotations or schema.

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?

The core statement is front-loaded and the cost/refusal policy follows logically. However, the cost material runs long and contains a duplicated phrase ('up to up to $0.06') and some redundancy between the estimate hold and the charging sentence.

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?

With an output schema present, return values need no explanation, and the description covers the remaining agent-critical unknowns: who is billed, cost ceiling, caching, the spend-limit hold, and the refusal-and-retry procedure. Nothing needed to call it correctly is missing.

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 coverage is 100% and the schema already defines sites (defaults to project plus competitors), projectId, and approvedMaxCostUsd including the 'never set without asking' rule. The description mostly restates those semantics, adding only the sequencing cue that a refusal precedes setting the approval amount. That is marginal added meaning over the schema.

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 description gives a specific verb and resource: it counts linking sites gained and lost over the last 30 days for the project and each tracked competitor, in one request. That scope distinguishes it from generic backlink tools, though it never names a sibling (e.g. get_backlink_gap) to route the agent explicitly.

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 is only implied through the scope sentence ('project and each tracked competitor'). There is no explicit when-to-use or when-not-to-use advice versus alternatives such as get_backlink_gap or get_backlinks_overview. The rest of the text is about cost and refusal handling, which is invocation mechanics rather than tool selection.

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