Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

delete_prompt_topic

Delete a prompt topic, cascading permanent removal of every prompt under it and their recorded responses; irreversible and returns prompts_deleted.

Instructions

Delete a prompt topic. Cascades: every prompt filed under it, and all of those prompts' recorded responses, are permanently deleted too. Returns prompts_deleted. Irreversible.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does well on the big-ticket item: it discloses that child prompts and all their recorded responses are permanently deleted, calls the action irreversible, and names the returned field (prompts_deleted). It says nothing about required permissions, whether the topic must be empty, or any confirmation step, which are material for an unannotated destructive tool.

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?

Four short sentences, front-loaded with the action, then the cascade risk, then the return value, then the irreversibility flag. Nothing is redundant and the most dangerous fact is stated before an agent commits.

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 destructive, zero-parameter, no-output-schema tool, the description covers what is destroyed, that it cannot be undone, and what comes back. Missing are authorization prerequisites and how the topic is selected, both of which an agent about to trigger an irreversible cascade would want.

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 declares zero parameters, so the baseline is 4 and the description neither needs nor provides per-parameter syntax. Notably it never explains how the target topic is identified (presumably implicitly from context or a path binding), which is the one semantic gap.

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?

Opens with a specific verb+resource ("Delete a prompt topic") and immediately scopes it by describing the cascade, which implicitly separates it from delete_prompt (single prompt) and delete_prompt_topic's create/update siblings. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 cascade warning gives an agent a real decision signal (if you only want one prompt removed, this tool is the wrong one), but no explicit when-to-use / when-not-to-use statement or named alternative is provided. Usage is implied by the destructive scope rather than guided.

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