Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_ai_visibility_share_of_voice

Compare your domain's AI visibility share of voice against competitors across tracked prompts, including rank, period-over-period change, and head-to-head prompt wins and losses.

Instructions

The aggregate share-of-voice view: your domain against its competitors across every tracked prompt, each domain ranked by share of voice (0–100 average visibility) with its change vs the preceding period, plus a head-to-head count of the prompts you win and lose against the top competitor. Use list_prompts / get_prompt_detail for the per-prompt breakdown.

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": "get_ai_visibility_share_of_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden, and it does describe the return content: ranked domains, 0–100 averages, change vs preceding period, and win/loss prompt counts. It omits the read-only nature, any account/plan prerequisites, and how the comparison period is determined — nontrivial gaps for an unannotated tool whose time window is undefined.

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?

Three sentences, front-loaded with the primary framing ('the aggregate share-of-voice view'), followed by output details and then the sibling hand-off. Every clause conveys content the agent could not otherwise infer; nothing is redundant.

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

Completeness4/5

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

With no parameters and no output schema, the description does the heavy lifting well by enumerating what comes back: rankings, changes, and head-to-head counts. The one unresolved question — what window the 'preceding period' corresponds to and how it is set — is left unstated since no parameter controls it.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate at the input layer. The only residual concern is that the implicit time period is neither a parameter nor explained, but that is a completeness issue rather than a parameter-semantics one.

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

Purpose5/5

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

Specific verb+resource ('share-of-voice view: your domain against its competitors across every tracked prompt') that is clearly a distinct aggregate from the per-prompt tools. The scope — all tracked prompts, ranked by 0–100 average visibility — makes it identifiable without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to list_prompts / get_prompt_detail when a per-prompt breakdown is needed, which is a clear alternative-selection rule. It does not address the other visibility siblings (history, mentions) or state when this tool is the wrong choice, so it stops short of full when/when-not guidance.

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