Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_prompt_detail

Show per-engine visibility for one prompt: runs, mentions, mention rate, and change vs. prior period across ChatGPT, Claude, Gemini, Perplexity, and Google AI; date range via preset or absolute dates.

Instructions

Per-engine visibility for a single prompt: runs, mentions, mention_rate (%) and the change in percentage points vs the preceding period, for each engine it runs on (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews, Google AI Mode), with totals across engines. For AI Overviews only a citation counts as a mention. Date range via preset or absolute from/to (defaults to last_28_days).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the exact return fields, the comparison basis (percentage-point change vs the preceding period), the engine set, and a non-obvious domain rule that only a citation counts as a mention for AI Overviews. It omits how the target prompt is identified, any permission/auth notes, and response shape, which keeps it from a 5.

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?

Front-loaded with what is returned, then the caveat, then the date default — good ordering with no filler. The first sentence is long and comma-chained, and the full engine enumeration could be compressed, but each element conveys real information.

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?

No annotations and no output schema mean the description must cover everything, and it covers outputs, comparison semantics, and the date default well. The critical omission is input identification: an agent reading this cannot tell how to specify the prompt or what to pass for preset vs absolute dates, which is a material gap for a detail-fetch 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?

The schema is an empty object, so the baseline would be 4, but the description asserts 'Date range via preset or absolute from/to' even though no such properties are declared — the caller gets no parameter names or accepted preset values. More importantly, it never explains how the single prompt is selected (ID, topic, URL), which is the one input this tool must take.

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?

States a specific verb+resource: per-engine visibility detail for a single prompt, naming the exact metrics (runs, mentions, mention_rate, change in pp) and the engine breakdown. It is clearly distinguishable from list_prompt_runs or get_ai_visibility_history by scope (one prompt, per-engine detail). It stops short of explicitly naming a sibling to use instead, so 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied by scope ('for a single prompt') rather than stated; there is no when-to-use/when-not guidance and no routing to alternatives like the keyword/page detail tools. The only explicit guidance is the date-range default (last_28_days), which is useful but operational rather than selection 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