Skip to main content
Glama

delete_playbook

Destructive

Permanently delete a playbook by ID, including its schedules and runs. Use when the user wants to remove an automation they no longer need.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds context beyond that by disclosing the cascade ('including its schedules and runs') and the permanence of the operation. It stops short of stating whether confirmation is required or whether deletion can be undone/restored.

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, zero filler, and the permanent/cascading nature is front-loaded before the usage hint. Nothing needs trimming.

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 delete tool with a supplied output schema absent but a trivial return, the definition covers purpose, irreversibility, and cascade effects. The only meaningful omission is how an agent should obtain or confirm the playbook ID before an irreversible call.

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?

There is one required parameter with 0% schema description coverage, so the description carries the burden. Saying 'by ID' clarifies that the id is the playbook identifier rather than something else, but adds no format, source, or lookup guidance (e.g., where to obtain the ID).

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?

States a specific verb and resource ('Permanently delete a playbook by ID') and adds the scope of what goes with it ('including its schedules and runs'). It does not explicitly contrast with adjacent tools like update_playbook or disconnect_playbook_from_trigger, but the resource is unambiguous enough to separate it from delete_agent or delete_report.

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?

'Use when the user wants to remove an automation they no longer need' gives a clear positive trigger condition. It offers no when-not guidance or alternatives — e.g., disabling schedules via disconnect_playbook_from_trigger or editing via update_playbook instead of an irreversible delete — so the agent must infer those boundaries.

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