Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_prompt_citations

Lists the domains and URLs AI engines cite for a prompt, flags your own pages, and counts citations so you can see which pages earn visibility and which competitors win them.

Instructions

The sources the AI engines cited when answering one prompt, aggregated over the range: own_domain plus every cited domain and URL flagged with is_own_domain and url_count — so you can see which of your pages earn citations and which competitors win them.

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

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?

No annotations exist, so the description carries the full burden, and it does disclose the output fields and the fact that results are aggregated over a range — useful behavioral context. It says nothing about whether this is a read-only lookup, how large the result set can get, or how 'the range' is determined, which matters for a zero-parameter tool. A 3 reflects real value added but a partial profile.

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?

One well-built sentence that front-loads the resource and then explains the payload fields and the business payoff. No filler, no restatement of the title. The trailing 'so you can see...' clause is justification for length but does useful framing work.

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?

For a no-parameter, no-output-schema list tool, the description covers what comes back reasonably well. However, the unresolved 'one prompt' versus zero-parameter mismatch leaves an agent unsure whether it can scope the query at all, and the absence of any sibling routing is a real gap in a 33-tool catalog.

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?

With zero parameters and 100% schema coverage the baseline is 4, and there is nothing parameter-related left to explain. The only drag is the opposite problem: the description references 'one prompt' and 'the range' as if inputs existed, so an agent may suspect it is missing required arguments 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?

Names a specific resource — the domains and URLs cited by AI engines in response to a prompt — and describes the shape of the result (own_domain, is_own_domain, url_count). That is concrete enough to distinguish it from list_prompt_runs or get_prompt_detail. It stops short of a 5 because it never says how it relates to those siblings or which prompt is being analyzed.

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 guidance and no named alternative, despite ~30 sibling list_* tools competing for the agent's choice. The clause 'so you can see which of your pages earn citations and which competitors win them' is a benefit statement, not a selection rule. An agent must guess when to call this versus list_prompt_runs or list_annotations.

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