Skip to main content
Glama

ADS Beast

seo_serp_analysis

Read-only

What ranks for a query and why: content types, featured snippets, AI overviews, People Also Ask. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.ua
keywordYesTarget search query.
languageNoLanguage code, e.g. en.ru
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 already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — it consumes 1 AI request — but says nothing about rate limits, latency, or result granularity beyond the enumerated sections.

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 compact fragments, front-loaded with the core question answered, and the cost note is clearly separated. The 'AI: 1 AI request' phrasing is terse to the point of being slightly cryptic but costs no space.

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 no output schema, the description usefully substitutes a partial return-value summary, and it covers the required keyword implicitly. However, with four parameters, one entirely undocumented (client_id) and no mention of geo/language defaults, an agent cannot fully predict scoping or cost of calls.

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 75% (geo, language and keyword are documented in-schema), so the schema carries most of the weight. The description adds no parameter guidance, and client_id remains completely undocumented in both places.

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 names a concrete verb+resource ('what ranks for a query and why') and enumerates the specific outputs — content types, featured snippets, AI overviews, People Also Ask — so an agent knows this is SERP composition analysis rather than rank tracking or keyword research.

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 explicit when-to-use statement, no exclusions, and no named alternative (e.g., vs. seo_keyword_rank_check for position tracking). The usage is only inferable from the output list, leaving the agent to guess at selection criteria among ~30 SEO siblings.

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.