Skip to main content
Glama

Delete prompt topic

delete-prompt-topic
Destructive

Delete a prompt topic. It must hold no prompts, archived ones included (an archived prompt keeps its topic); move-prompt-to-topic moves them out. Confirm with the user first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain_id": "<domain_id>",
      "topic_id": "<topic_id>"
    },
    "name": "delete-prompt-topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topic_idYesTopic ID from list-prompt-topics
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / topic_id / description
      Previous value: -"Topic ID"New value: +"Topic ID from list-prompt-topics"
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / topic_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds non-obvious operational context: the tool fails unless the topic is empty, and archived prompts still count as occupying the topic. It also imposes a human-confirmation step, which is behavior an agent cannot infer from the annotation set alone.

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?

Three short sentences with zero filler: action, constraint with rationale in parentheses, alternative, and a confirmation directive. The precondition and the safety directive are front-loaded rather than buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-required-parameter destructive tool with annotations and no output schema, everything an agent needs is present: what it does, the blocking constraint, how to unblock it, and the confirmation requirement. Nothing material is left to inference.

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?

Schema description coverage is 100% and both parameters (topic_id, domain_id) are documented in the schema with provenance hints ('from list-prompt-topics', 'from list-domains'). The description adds no further parameter meaning, so the baseline 3 applies.

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 prompt topic') and immediately scopes it with the precondition that the topic must hold no prompts. An agent can distinguish it from create-prompt-topic and update-prompt-topic purely from the name and first sentence.

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

Usage Guidelines5/5

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

Explicitly names when deletion is valid (topic empty, archived prompts counted), when it is not (any prompt present), the alternative that resolves the blocker ('move-prompt-to-topic moves them out'), and a procedural requirement ('Confirm with the user first'). This covers when, when-not, and alternatives in three sentences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources