Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

Delete a prompt

delete_prompt
DestructiveIdempotent

Permanently delete a prompt by its ID using the ID returned from list_prompts. Use this to remove prompts you no longer need; deletion cannot be undone through tools.

Instructions

Delete a prompt by its id. This cannot be undone through the tools.

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": {
      "id": "<id>"
    },
    "name": "delete_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrompt ID, as returned by list_prompts

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
versionYes
persistedYesTrue when the change was saved to the state directory, false when it is in memory only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"Prompt ID"New value: +"Prompt ID, as returned by list_prompts"
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "True when the change was saved to the state directory, false when it is in memory only",
      +      "type": "boolean"
      +    },
      +    "version": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "version",
      +    "persisted"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv4.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv4.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is low. The description still adds genuinely new information by scoping the irreversibility ("cannot be undone through the tools"), which tells the agent there is no in-toolset recovery path. It omits secondary effects, such as what happens to anything referencing the deleted prompt.

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 short sentences with no filler, and the irreversibility warning is front-loaded right after the operation statement. Every clause carries information the agent needs.

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 single-parameter destructive tool, the essentials are present: the operation, the required id, and the irreversibility caveat. An output schema exists so return values need no explanation, though the description could note whether deletion affects dependent records.

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 coverage is 100% and the id property is already documented as "Prompt ID, as returned by list_prompts." The description adds only the phrase "by its id," which conveys no format or sourcing detail beyond what the schema gives, so the baseline 3 applies.

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?

The description gives a specific verb+resource ("Delete a prompt") and the identifier needed ("by its id"), so the agent can tell this removes an existing prompt rather than reading or modifying it. It stops short of explicitly contrasting with siblings such as update_prompt, so a 4 rather than a 5.

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 operation itself and by "by its id," which points at ids obtained elsewhere (list_prompts), but no when-to-use or when-not-to-use condition is stated. It never says, for example, to prefer update_prompt when the goal is modification rather than removal.

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