Skip to main content
Glama

delete_trigger

Destructive

Permanently removes a trigger by UUID and stops its configured automation, cleaning up unused or obsolete trigger configurations.

Instructions

Permanently remove a trigger and stop its configured automation.

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": {
      "trigger_id": "<trigger_id>"
    },
    "name": "delete_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
trigger_idYesUUID of the trigger to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger a remover"New value: +"UUID of the trigger to remove"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds behavior beyond that: removal is permanent and it stops the trigger's configured automation, clarifying the side effect. It still omits what happens to existing execution history or whether a confirmation/error path exists.

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?

A single front-loaded sentence with no filler; both the action and its immediacy are stated first. Nothing is redundant or padded.

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 one-parameter destructive tool with annotations and no output schema, the definition is nearly sufficient: it conveys permanence and the automation side effect. It doesn't address failure modes (nonexistent trigger) or downstream effects on execution 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?

Only one parameter (trigger_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds nothing about the identifier, which is acceptable at this coverage level.

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?

Names a specific verb and resource ("Permanently remove a trigger") and the effect ("stop its configured automation"), which distinguishes it from sibling delete_* tools operating on other resources and from create_trigger/update_trigger/toggle_trigger.

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?

The word "Permanently" implies the when-to-use contrast with toggle_trigger (temporary disable), but no alternative or prerequisite is named explicitly. An agent can infer the distinction, though it isn't stated.

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

Deploy Server

Other Tools