Skip to main content
Glama

Rankings: track search terms for a client

rank_track
Idempotent

Track where a client ranks on Google for up to 10 search terms: the Search Console position every day, and the map-pack (Google Maps) position every Monday once a city is given. With no terms and nothing tracked yet, it picks the client's best Search Console queries. Returns the first reading at once; rank_report shows movement after that. Removing a term only stops tracking it.

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": {
      "client": "<client>"
    },
    "name": "rank_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity and state for the map-pack check, e.g. 'Boise, ID'. Needed once; finds the client's Business Profile on the map.
termsNoSearch terms to add, as a customer types them, e.g. 'fence installation boise'
clientYesClient name from list_clients
removeNoTracked terms to stop tracking
confirmNoAdding terms or a city: leave false to preview; set true after the person agrees. Removing terms or just reading needs nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Adding terms or a city: leave false to preview; set true after the person agrees. Removing terms or just reading needs nothing.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare write (readOnlyHint=false), idempotent, non-destructive and open-world behavior, so the bar is lower. The description adds valuable beyond-annotation context: the daily/weekly measurement cadence, immediate first reading, and that removal 'only stops tracking it' (consistent with destructiveHint=false). It does not mention the preview/confirm commit flow, which the schema carries instead.

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?

Four dense sentences, front-loaded with the core action and cadence, then defaults, return behavior, and removal semantics. No filler or redundancy.

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?

No output schema exists, and the description appropriately describes the return ('returns the first reading at once') and points to rank_report for ongoing movement. Combined with a fully documented schema, an agent has what it needs, though the write-confirmation flow is only implied via the schema.

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 baseline is 3, but the description adds real meaning: the 10-term cap, that city is needed once for the Monday map-pack check, and that removing a term merely halts tracking. It stops short of detailing the confirm preview-then-commit semantics, which lives in the schema.

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 (track Google rank for a client's search terms) with concrete scope: Search Console daily position and map-pack weekly position. It also names the sibling rank_report and contrasts its role, so the agent can distinguish the two without opening schemas.

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?

Explicitly covers the key edge cases: 'With no terms and nothing tracked yet, it picks the client's best Search Console queries,' and routes movement reporting to rank_report ('rank_report shows movement after that'). It also clarifies that removal is a stop-tracking action rather than a data deletion.

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.