Skip to main content
Glama

Visibility Genies

Find link competitors

find_link_competitors

Finds the 20 sites that share the most linking sites with a domain: rivals for the same links, to track as competitors (save_competitor) or compare in get_backlink_gap. Estimated price: up to $0.05, one backlinks request billed by the rows returned. An answer saved for the domain within 7 days 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": "find_link_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoThe site whose links are matched. Defaults to the project's.
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.1/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the price ceiling (~$0.05, billed by rows returned), the 7-day free cache read, the default $2.00 workspace agent spend limit, the hold of estimate-plus-margin during execution, and the pre-purchase refusal behavior. The only mild ambiguity is that readOnlyHint=false is never reconciled with the apparent read-and-cache nature of the call.

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-loads the purpose in the first clause and keeps cost mechanics in one dense but ordered block. The spend-limit sentence chain ('it holds at most its estimate plus a margin while it runs and is charged what it bought, never more') is slightly over-explained but each clause carries distinct information.

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?

Output schema exists, so return values need no explanation, and cost, caching, spend-limit refusal, and follow-up routing are all covered. The one omission for a tool with several near-siblings is an explicit contrast with find_serp_competitors.

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%, so the schema already documents domain, projectId, and approvedMaxCostUsd in detail. The description adds useful context about the refusal-then-retry loop that motivates approvedMaxCostUsd, but nothing about formats or defaults beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Finds the 20 sites that share the most linking sites with a domain'), even fixing the result size and the conceptual framing ('rivals for the same links'). It also names the two concrete follow-up tools (save_competitor, get_backlink_gap), so the agent knows what to do with the output.

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 context for use and explicit next steps ('to track as competitors or compare in get_backlink_gap'), plus the full recovery path when a call is refused for exceeding the spend limit. It stops short of excluding the ambiguous sibling find_serp_competitors, so the agent must infer that SERP rivals differ from link rivals.

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