Skip to main content
Glama

Visibility Genies

Add rank tracking keywords

add_rank_tracking_keywords

Add keywords to an existing rank tracker. This buys nothing and starts no check. On a scheduled tracker first show the user the price from estimate_rank_tracker_cost and pass that figure as maxEstimatedScheduledCheckCredits. A scheduled tracker buys its checks only under the user's approval of its settings, given on the tracker's page: without one its schedule is paused, buying nothing, until they approve there (scheduleAwaitsApproval). Keywords already tracked and repeats are skipped; added is the number really added.

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>",
      "keywords": "<keywords>"
    },
    "name": "add_rank_tracking_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to start tracking.
matchCaseNoTrack keywords exactly as typed instead of lowercasing them. A keyword with capitals is tracked and billed separately from its lowercase form.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackerIdYesTracker id from get_rank_tracker.
maxEstimatedScheduledCheckCreditsNoNeeded for a scheduled tracker: the scheduled figure estimate_rank_tracker_cost returns as costCredits, passed once the user has seen that recurring price. The keywords are refused when a check would cost more. It does not approve the schedule: the user does that on the tracker's page.

Output Schema

NameRequiredDescriptionDefault
metaNo
addedYes
addedIdsYes
requestedYes
trackerIdYes
scheduledEstimateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it clarifies no checks are purchased, that a scheduled tracker stays paused (scheduleAwaitsApproval) until approved on its page, that duplicates are skipped, and that `added` is the true count. That is more than a minimum, but it stops short of describing the response shape or any rate limits, so it sits between adequate and rich.

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?

Front-loaded with the core action and the key non-effect, then the approval caveat. Dense and mostly efficient, though the mid-description sentence about scheduled approval is long and carries a parenthetical flag, which slightly hurts scanning.

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?

An output schema exists, so return values need no explanation, and the description still clarifies the `added` field. For a 5-parameter mutation with full schema coverage, nothing an agent needs 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.

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. The description still adds meaning the schema does not: where the maxEstimatedScheduledCheckCredits figure must come from (estimate_rank_tracker_cost), that exceeding it causes refusal, and that passing it does not itself approve the schedule.

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 ("Add keywords to an existing rank tracker") and immediately scopes the effect ("This buys nothing and starts no check"), which lets an agent distinguish it from cost-estimation and check-running siblings.

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?

Gives explicit conditional guidance: on a scheduled tracker, first show the price from estimate_rank_tracker_cost and pass it as maxEstimatedScheduledCheckCredits, and note that approval happens on the tracker's page rather than through this call. Also covers the duplicate/repeat case, so there is little left to infer.

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