Skip to main content
Glama
Sign In
SEOctopus

SEOctopus

by itsjwill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

competitive_serp_share

Calculate your share of search engine results page (SERP) real estate against competitors for specific keywords. Identify gaps and optimize visibility.

Instructions

Calculate your share of SERP real estate vs competitors

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": {
      "keywords": "<keywords>",
      "domain": "<domain>"
    },
    "name": "competitive_serp_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to check
domainYesYour domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as data requirements, rate limits, or side effects. The description only states the basic function without elaborating on what 'share' means or how it is computed.

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?

The description is a single sentence that is concise and front-loaded with the core action. No extraneous information is included.

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?

Given the lack of output schema and annotations, the description is too minimal. It does not explain what the output represents (e.g., percentage, number of features), nor does it provide context about the scope of 'SERP real estate' (e.g., organic vs paid). The tool's complexity is low, but completeness is still lacking for a calculation tool.

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 100% with descriptions for both parameters ('Keywords to check' and 'Your domain'). The tool description adds no additional meaning beyond these basic schema descriptions, so the baseline score of 3 is appropriate.

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 clearly states the tool calculates a share of SERP real estate versus competitors, using 'calculate' as a specific verb and specifying the resource. It distinguishes from sibling tools like rank_competitors and competitive_analyze, though 'SERP real estate' could be more precisely defined.

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?

No guidance on when to use this tool versus alternatives such as competitive_analyze or competitive_content_gap. No prerequisites or contextual conditions are provided, leaving the agent to infer usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools