Skip to main content
Glama

Visibility Genies

Save a link prospect

save_link_prospect
Destructive

Adds a site to the project's link prospects, or changes a kept one's status or note. Uses no credits and calls no provider. A site already kept is never added twice: only the competitors it newly links to are added, and its status and note change only when given; a note given replaces the one kept. A site this tool adds is recorded as added by hand, without rank passed, spam score or backlinks. Adding it on the Backlink Gap page (or from a competitor's referring domains on the Backlinks page) keeps them, and fills them in for a site already kept without them, so point the user there when those metrics matter. The project's own domain and sites marked for disavow in Backlinks are refused.

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>",
      "domain": "<domain>"
    },
    "name": "save_link_prospect"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoReplaces its note. An empty string clears it.
domainYesThe site, e.g. 'example.org'. www. and any path are dropped.
statusNoIts new status. A new prospect starts at to_contact. Ask the user before changing one.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsNoCompetitor domains the site links to, e.g. from get_saved_backlink_gap. Only ones not already kept are added.

Output Schema

NameRequiredDescriptionDefault
metaNo
addedYes
prospectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=false), the description discloses cost ('Uses no credits and calls no provider'), upsert/idempotency semantics ('never added twice'), note replacement behavior, what metadata is omitted ('without rank passed, spam score or backlinks'), and two refusal cases (own domain, disavow-marked sites). This is substantial behavioral context the annotations cannot convey.

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 action and the no-credit/no-provider fact are front-loaded, and every sentence carries information. Some sentences are long and clause-heavy (the Backlink Gap sentence in particular), which slightly hurts scannability, but there is no filler.

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?

For a mutating upsert tool with an output schema already documenting returns, the description covers side effects, idempotency, refusals, cost, and the alternative path for richer metrics. Nothing an agent needs to invoke it correctly is missing.

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: competitors are only added when newly linked, status/note change only when supplied, and a given note replaces the kept one. It does not restate the enum values or the domain normalization rule, which the schema already covers.

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?

The first sentence names a specific verb and resource ('Adds a site to the project's link prospects') and also covers the update case ('changes a kept one's status or note'), which cleanly separates it from the read-only sibling list_link_prospects. An agent can tell what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent elsewhere when richer data is needed: 'Adding it on the Backlink Gap page (or from a competitor's referring domains on the Backlinks page) keeps them... so point the user there when those metrics matter.' It also states a consent rule ('Ask the user before changing one') and the refusal conditions, giving clear when-to-use and when-not-to-use guidance.

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