Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_prompt_runs

Retrieve individual AI engine runs for a prompt, including date, engine, mention flags, and response excerpts; filter by engine or date range and paginate results.

Instructions

The individual engine executions behind one prompt — one row per run with date, engine, mentioned / mentioned_in_text flags and a response_excerpt (up to 600 chars of the actual AI answer). Filter by engine, scope by date range, paginate via limit (max 200) and next_cursor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the returned fields, the 600-character excerpt cap, the 200-row limit maximum, and cursor-based pagination. It stops short of stating whether it errors on a missing prompt or what ordering the rows arrive in.

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 dense sentence whose payload (what a row is) is front-loaded, followed by the filtering and pagination controls. Every clause carries information, though the mid-sentence field enumeration makes it slightly harder to scan than a short bulleted structure would.

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?

There is no output schema and no annotations, so the description must do everything, and it covers return shape and paging well. The notable gap is that it never says how the target prompt is identified (no prompt id parameter appears in the schema), which an agent needs before it can call this correctly.

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 input schema is an empty open object, so the description is the only source of parameter meaning, and it supplies it: engine filter, date-range scoping, limit with an explicit max of 200, and next_cursor. It does not give the date format or the cursor's provenance, so it falls short of a 5.

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?

States a specific verb and resource ('individual engine executions behind one prompt') and immediately defines the row shape (date, engine, mentioned flags, response_excerpt), which clearly separates it from prompt-level siblings like list_prompts and get_prompt_detail.

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 the framing 'behind one prompt' and the filter/pagination hints, so an agent can infer this is the drill-down call after listing prompts. However, no sibling is named and there is no explicit when-not-to-use guidance, leaving routing to inference.

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