Skip to main content
Glama

Visibility Genies

Read the disavow list

get_disavow_list
Read-only

Reads the sites and links the project marked to disavow on the Backlinks page, each with when it was marked, and the disavow file they make for Google Search Console. Read only: no agent tool marks or unmarks one. Uploading the file replaces the list Search Console holds. 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": "get_disavow_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
linksYes
sitesYes
fileTextYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety bar is partly covered. The description still earns credit by adding non-annotation facts: no tool in the set mutates the list, uploading overwrites what Search Console holds, and the call consumes no credits and contacts no provider. A 4 rather than 5 only because it omits any note on volume, pagination, or behavior when the list is empty.

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

Conciseness5/5

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

The core scope is front-loaded in the first clause, followed by three short sentences that each contribute a distinct fact (read-only guarantee, upload overwrite risk, zero credit cost). No filler or restatement of the title.

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, the description needn't enumerate return fields, yet it still summarizes the payload (sites, links, mark dates, disavow file). For a single-parameter, read-only tool with full schema coverage, nothing an agent needs in order 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?

There is a single parameter at 100% schema description coverage, and the schema already explains projectId as the billed project with a pointer to list_projects. The description adds nothing about the parameter, which is acceptable when the schema carries it fully, 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 (Reads) and a precisely scoped resource: sites and links the project marked to disavow on the Backlinks page. It goes further to name what comes back (mark dates and the disavow file for Google Search Console), so an agent knows exactly what this returns without opening the output schema.

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 scope: read the disavow list rather than the broader backlink profile tools. It adds a useful boundary ('Read only: no agent tool marks or unmarks one') and a caution about uploading replacing the Search Console list, but it never names an alternative sibling or an explicit when/when-not condition.

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