Skip to main content
Glama

disconnect_playbook_from_trigger

DestructiveIdempotent

Stop a playbook using a trigger. Saves on the playbook's working copy; it takes effect when the playbook is published, and until then the trigger keeps sending it items. When it takes effect, items still waiting for that playbook are closed as "never ran". A trigger can only be deleted once no published playbook uses it.

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": {
      "triggerId": "<triggerId>",
      "playbookId": "<playbookId>"
    },
    "name": "disconnect_playbook_from_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerIdYesThe trigger's id, from list_triggers or create_trigger.
playbookIdYesThe playbook to disconnect, from list_playbooks.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/not-read-only; the description goes well beyond by explaining that the change is written to the working copy, does not take effect until publish, that the trigger keeps delivering items until then, and that queued items are closed as 'never ran'. That is exactly the kind of side-effect and timing detail an agent needs before making a destructive call.

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, front-loaded with the action, followed by timing and then consequence. No filler and nothing repeated from the schema.

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 two-parameter destructive mutation with no output schema, the description covers timing (publish-gated), side effects on queued items, and the related delete constraint. Nothing an agent needs in order to call it safely is missing.

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 both parameters already carry descriptions naming their source (list_triggers/create_trigger, list_playbooks). The prose adds no further meaning about the ids, so the baseline of 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 opening sentence gives a specific verb and object: 'Stop a playbook using a trigger,' which is the clear inverse of the sibling connect_playbook_to_trigger. It does not explicitly name that sibling, but the operation is unambiguous from the verb alone.

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 rather than stated: the closing note that a trigger can only be deleted once no published playbook uses it hints at when this tool is needed, and the pending-items note hints at consequences. However, there is no explicit 'use this instead of pause_trigger/delete_trigger when...' guidance, so the agent must infer the alternative.

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