Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_ai_visibility_mentions

Track how often a brand is named across tracked AI prompts, with counts and percentages for mentioned, mentioned in text, and absent—showing presence, not sentiment.

Instructions

How often the brand is named across all tracked prompts in the range: total_prompts plus three mutually exclusive buckets — mentioned (named prominently), mentioned_in_text (only in the body of the answer) and absent — each with a count and a percentage. This is presence, not sentiment.

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_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return taxonomy: mutually exclusive buckets with counts and percentages, plus the 'presence, not sentiment' caveat. It leaves unexplained how 'the range' is determined given the tool takes zero parameters, which is a meaningful behavioral gap an agent cannot resolve elsewhere.

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?

A single dense sentence that front-loads the core measure and then defines each bucket. Every clause carries information, though the bucket enumeration makes it slightly harder to scan than a short lead sentence followed by a compact list.

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?

Because there is no output schema, the description must explain return values, and it does so thoroughly, including bucket exclusivity. However, for a tool with no parameters, the unexplained notion of 'in the range' leaves the agent unsure what window the counts cover, which is a real completeness hole.

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?

The tool has zero parameters, so there is no schema detail to add meaning beyond; the baseline for a parameterless tool is 4. The description's mention of 'the range' is the only wrinkle, since it implies an input that the schema does not expose.

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 a specific measure ('how often the brand is named across all tracked prompts') with a named resource, and enumerates the output buckets, so an agent knows exactly what this returns. It distinguishes the tool from sentiment-oriented siblings via 'This is presence, not sentiment', but does not explicitly separate it from share_of_voice or history.

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 framing, no when-not-to-use, and no named alternative. The phrase 'across all tracked prompts' implies scope, but nothing tells the agent why it would choose this over get_ai_visibility_share_of_voice or get_ai_visibility_history.

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