Skip to main content
Glama

ADS Beast

seo_keywords_track

Checks positions now, records them and reports changes and quick wins. AI: 1 AI request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_keywords_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.ua
domainNoDomain without scheme.
keywordsNoKeywords, comma-separated; the stored list by default.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and 'records them' is consistent with that, so no contradiction. It adds a useful cost signal ('AI: 1 AI request') that annotations don't cover, but says nothing about what is stored, how repeated runs affect prior records, or permission/auth needs.

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?

Two short sentences with no filler, and the outcome (changes and quick wins) is front-loaded before the cost note. 'Quick wins' is left unexplained, which is the only wasted ambiguity in an otherwise tight definition.

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

Completeness3/5

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

With four all-optional parameters and no output schema, the definition should clarify what a run with no domain or keywords does and what 'changes and quick wins' contain. It gives a rough sense of the result but leaves defaulting behavior and return shape underspecified.

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 coverage is 75%, so most parameters are already documented. The description adds only that positions are checked 'now' rather than explaining geo defaults, whether domain and keywords are both needed, or what client_id scopes, so it does not materially extend the schema.

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?

The description gives concrete verbs (checks positions, records, reports changes and quick wins), which distinguishes it from a pure rank-check tool by implying persistence of history. It never names the resource explicitly, relying on the tool name 'seo_keywords_track', and doesn't name the closely related siblings like seo_keyword_rank_check or seo_rank_changes.

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?

'Checks positions now' hints that this is an immediate, state-changing run, but there is no explicit when-to-use guidance and no mention of alternatives for pure historical reporting or non-persisting checks. The agent must infer routing from sibling names alone.

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.