Skip to main content
Glama

Visibility Genies

List link prospects

list_link_prospects
Read-only

Lists the project's link prospects, the sites it wants a link from, newest first: each with the competitors it links to, its status (to_contact, contacted, won, lost), notes, and its rank passed (the rank its links pass to the competitors, a 0 to 100 link-graph score, not a Google metric, which sitewide links inflate), average link spam and backlinks as its table showed them when it was added or filled in, with how many stand at each status. A prospect whose site, or a site it is part of, was marked for disavow in Backlinks after it was added is flagged disavowed, and one the project's saved referring domains list as already linking to it is flagged links to you: each is kept until the user removes it. Uses no credits and calls no provider.

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": "list_link_prospects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many prospects to return, newest first. Defaults to 200.
offsetNoHow many to skip, to read further on.
statusNoOnly the prospects with this status. Omit for all.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsYes
countsYes
totalCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, yet the description adds substantial behavior the agent could not infer: newest-first ordering, per-row contents, the definition and range of "rank passed" (0-100, not a Google metric, inflated by sitewide links), and the semantics of the disavowed and "links to you" flags. It also discloses retention ("each is kept until the user removes it") and cost behavior, which is exactly the value-add expected beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the opening clause, which is good, but the whole definition is a single sprawling sentence with stacked parentheticals ("the rank its links pass to the competitors, a 0 to 100 link-graph score, not a Google metric, which sitewide links inflate") that is hard to parse on first read. The content mostly earns its place, but restructuring into shorter sentences would improve it.

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?

For a read-only list tool with an output schema, full schema coverage, and clear annotations, the description covers everything an agent needs to call it correctly, including flag semantics that may not be self-evident from the payload. Some return-field explanation overlaps with the existing output schema, which is the only real inefficiency.

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, status, and projectId are already fully documented in the schema. The description adds no syntax or formatting detail for these parameters and only indirectly references status aggregation ("how many stand at each status"), so the baseline 3 applies.

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 ("Lists the project's link prospects, the sites it wants a link from") plus ordering (newest first), so an agent knows exactly what it returns. It never names a sibling such as find_link_competitors or get_disavow_list to delineate boundaries, which keeps it from a 5.

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 implied by the resource description (read the prospect pipeline), and the cost note "Uses no credits and calls no provider" helps an agent decide to call it freely. There is no explicit when-to-use/when-not guidance and no routing to alternatives like the competitor-link 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