Skip to main content
Glama

Visibility Genies

Read a saved backlink gap

get_saved_backlink_gap
Read-only

Reads a backlink gap saved by the Backlink Gap page or get_backlink_gap, however old, a page of prospects at a time, for free. It never buys: a competitor not saved for the domain is named with the price get_backlink_gap would pay for it.

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>",
      "competitors": "<competitors>"
    },
    "name": "get_saved_backlink_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many referring domains to return, best prospects first: those linking to the most competitors, then the strongest, with those whose average link spam is above 60 (the high band) last. Defaults to 100.
domainNoYour domain. Defaults to the project's own.
offsetNoHow many of the best prospects to skip, to read further on.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsYes1 to 4 competitor domains, e.g. ['example.org'].

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsNo
savedNo
domainNo
competitorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely new behavior: the call is free, performs no purchase, and returns unsaved competitors named with the price get_backlink_gap would pay, which tells the agent to expect partial/incomplete prospect rows with pricing annotations.

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?

A single densely packed sentence that front-loads the action and scope before the cost clause. It is efficient with no filler, though the stacked clauses ('however old, a page of prospects at a time, for free') cost a little readability.

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?

Return values are covered by the output schema and safety by the annotations, leaving the description responsible only for the unusual semantics: free reads, paged access, and unpurchased competitors carrying price. All of that is present, so an agent has everything needed to call this correctly.

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 description coverage is 100%, so limit, offset, domain, projectId and competitors are all documented, including the 'best prospects first' ordering that already appears on limit. The description only reinforces paging ('a page of prospects at a time') and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Reads a backlink gap saved by the Backlink Gap page or get_backlink_gap') and pins the scope: any age, paged, free. It implicitly separates itself from get_backlink_gap, the tool that computes fresh gaps, so an agent can pick between them without opening either schema.

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?

Usage is conveyed through the cost/ownership model: this reads what was already saved 'however old, a page of prospects at a time, for free', while get_backlink_gap is the tool that would pay for a fresh competitor. Exclusion is stated clearly ('It never buys'), but the when-to-prefer-this-vs-get_backlink_gap choice is left to inference rather than spelled out.

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