Skip to main content
Glama

ADS Beast

seo_competitor_analysis

Read-only

Competitors' search presence, content strategy, links and AI visibility, with gaps and opportunities. 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": {
      "competitors": "<competitors>"
    },
    "name": "seo_competitor_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry: SK.
nicheNoBusiness niche or industry, in plain words.
domainNoDomain without scheme.
client_idNo
competitorsYesUp to three competitor domains, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely useful non-schema fact — the cost ('AI: 1 AI request') — but says nothing about data sources, freshness, how long the analysis takes, or whether results are cached, which matters for an expensive open-world analysis.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, but the telegraphic fragment style ('Competitors' search presence, ...') front-loads a list rather than a statement of purpose, and the trailing 'AI: 1 AI request.' reads as an unexplained addendum rather than structured context.

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?

With five parameters, no output schema, and a multi-dimensional analysis return, the description should explain what the produced report contains and how the scoping inputs shape it. Instead it only names the covered topics and a cost figure, so the agent cannot predict the result or judge scope.

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 80%, so parameters are largely documented in the schema and the baseline is 3. The description adds no parameter-level meaning — it never mentions the competitor limit (three), the geo/domain/niche scoping, or what client_id ties to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the subject matter it covers ('competitors' search presence, content strategy, links and AI visibility') but is a noun phrase with no verb, so the agent must infer that this is an analysis/report generator rather than an action. It does not differentiate from adjacent siblings such as seo_backlink_analysis, competitor_aeo_benchmark or competitor_site_analyze, which overlap heavily with the listed dimensions.

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 when-to-use or when-not-to-use guidance at all. With multiple overlapping competitor/SEO siblings, the description gives the agent nothing to route on besides the enumerated topics, leaving selection to guesswork.

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.