Skip to main content
Glama

Visibility Genies

Remove rank tracking keywords

remove_rank_tracking_keywords
Destructive

Stops tracking keywords on a rank tracker while keeping their position history. IDs that are unknown, stale, from another tracker or repeated are skipped, so removed may be smaller than requested. Uses no credits.

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>",
      "trackerId": "<trackerId>",
      "keywordIds": "<keywordIds>"
    },
    "name": "remove_rank_tracking_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackerIdYesTracker to change, from get_rank_tracker.
keywordIdsYestrackingKeywordId values (from get_rank_tracker) of the keywords to drop.

Output Schema

NameRequiredDescriptionDefault
metaNo
removedYes
requestedYes
trackerIdYes
removedIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context those annotations cannot convey: history is retained, invalid/duplicate IDs are silently skipped so `removed` may be less than `requested`, and the call consumes no credits. The one gap is that it doesn't say whether skipping is reported per-ID or how failures surface, but the safety and cost profile are well covered.

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?

Two tight sentences with the primary behavior front-loaded and the consequence ('`removed` may be smaller than `requested`') following immediately. No filler or redundant restatement of the title.

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 annotations carry the destructiveness signal. The description completes the picture with history retention, skip semantics, and zero credit cost. Slightly more detail on prerequisites or result reporting would make it fully complete for a destructive mutation.

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 projectId, trackerId, and keywordIds are already fully documented including their source tools. The description's mention that unknown, stale, or foreign-tracker IDs are skipped adds semantic meaning to keywordIds, but it does not go beyond that; baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Stops tracking keywords on a rank tracker') and adds a scoping distinction ('while keeping their history') that separates it from a hard delete. It does not explicitly name the sibling add_rank_tracking_keywords as the inverse operation, so differentiation is implied by the verb rather than stated.

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 verb and by the note that unknown, stale, foreign, or repeated IDs are skipped, which tells the agent tolerant input is acceptable. However, there is no explicit when-to-use statement, no prerequisite guidance (e.g. call get_rank_tracker first to obtain valid IDs), and no named alternative for permanently purging history.

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