Skip to main content
Glama

AgentSEO Rank Track

agentseo_rank_track
Destructive

Queue a rank tracking check for a URL and keyword.

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": {
      "keyword": "<keyword>",
      "url": "<url>"
    },
    "name": "agentseo_rank_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to track
syncNo
keywordYesKeyword to track
locationNoUnited States

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The annotations declare destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description explains none of these: no cost/credit implication, no note that each call creates a distinct non-idempotent job, and no explanation of why a rank check is flagged destructive. The single word 'Queue' does disclose asynchronous behavior, which is genuine added value, but the sync default of true complicates that story and the description never clarifies immediate vs. deferred execution.

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?

A single front-loaded sentence with no wasted words and the key qualifiers (URL, keyword) up front. It is efficient, though the terseness is part of why behavioral and parameter detail is missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, non-idempotent, destructive, open-world mutation with no output schema, the agent needs to know that a job is created and must be checked with agentseo_job_status, and what the call returns. None of that is present, so an agent could invoke it correctly but has no idea what happens next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: url and keyword are documented in the schema and merely echoed by the description. The two undocumented parameters, sync (defaulting true) and location (defaulting 'United States'), receive no meaning from the description at all, leaving the async/sync distinction and geo-scoping unexplained.

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?

Specific verb ('Queue') plus a concrete resource ('rank tracking check') scoped to a URL and keyword, which separates it from sibling read tools like agentseo_serp_volatility or agentseo_local_visibility_track. It stops short of naming how it differs from those siblings, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives (e.g. agentseo_local_visibility_track, agentseo_serp_volatility), no prerequisites, and no mention that the queued job must subsequently be polled via agentseo_job_status. Usage is only implied by the word 'Queue'.

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.