Remove a prompt from your saved collection by its ID to keep your AI prompt library organized and current.
Remove um prompt da coleção pelo ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID do prompt a ser removido |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden. It implies a destructive mutation but says nothing about permanence, reversibility, required permissions, or side effects on related data — all critical for a delete tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler. For a one-parameter tool, this is appropriately sized and wastes no tokens.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is structurally simple (one param, no output schema) and the schema handles the input, but a destructive operation with no annotations leaves the agent without essential context about irreversibility or confirmation requirements.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter, and schema coverage is 100%, so the schema already documents 'id' as 'ID do prompt a ser removido'. The description's 'pelo ID' adds no meaning beyond that, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Remove um prompt') plus the scoping key ('pelo ID'), so the operation is unambiguous. It does not explicitly contrast itself with siblings like update_prompt, but 'remove' is distinct enough that differentiation is not strictly needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use, when-not-to-use, or prerequisite information is provided. It doesn't say whether the removal is permanent, whether confirmation is needed, or what to do instead if the prompt should merely be modified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.