Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

delete_prompt

Deletes a tracked prompt and all recorded engine responses, leaving its topic untouched. Use it to remove stale AI-visibility prompts; the action is irreversible.

Instructions

Delete a tracked prompt and all of its recorded engine responses. Irreversible; the prompt's topic is left untouched.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/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 behavioral burden and does well: it discloses that deletion cascades to recorded engine responses and that the action is irreversible. It stops short of stating permission requirements or whether a confirmation step exists, which matters for an unrecoverable operation.

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?

Two sentences, no filler, and the destructive scope is front-loaded ahead of the irreversibility warning. Every clause carries information an agent needs before calling.

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?

For a zero-parameter destructive tool with no output schema, the description covers what is destroyed, what survives, and that it cannot be undone. Only authorization prerequisites and the response shape are absent, which are secondary for a tool this simple.

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. The empty schema leaves nothing to disambiguate, and the description adds no parameter-level noise that would conflict with it.

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 ('Delete a tracked prompt') and immediately scopes the blast radius ('all of its recorded engine responses'), which distinguishes it from delete_prompt_topic by noting the topic survives. An agent can tell what is removed and what is not without opening anything else.

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?

The clause 'the prompt's topic is left untouched' implicitly steers an agent toward delete_prompt_topic for topic removal, but the description never names an alternative or states a when-to-use condition. Guidance is inferable rather than explicit.

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