Skip to main content
Glama

resume_trigger

DestructiveIdempotent

Resume a paused trigger: it starts checking again on its schedule, and the playbooks that use it start getting items again. Use when re-enabling a paused trigger after confirming with the user.

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>"
    },
    "name": "resume_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerIdYesThe trigger's id, from list_triggers or create_trigger.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is partly covered. The description adds genuine context beyond that: the downstream consequence for connected playbooks and a requirement to confirm with the user. It stops short of explaining what happens to items accumulated during the pause, which is likely the reason for the destructive flag.

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 sentences, zero filler. The core action and its effect come first, with the usage caution second, so an agent gets the essentials from the opening clause alone.

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 toggle with no output schema and annotations covering idempotency and destructiveness, the definition supplies action, effect and precondition. The only meaningful omission is what happens to backlogged items on resume, which is relevant given destructiveHint=true.

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 a single parameter with 100% schema coverage, including a description pointing to list_triggers or create_trigger as the source of the id. With the schema doing the full job, a baseline 3 is appropriate; the description adds no further parameter meaning.

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?

"Resume a paused trigger" is a specific verb plus resource, and the follow-on clause explains the observable effect: it resumes scheduled checking and playbooks start receiving items again. This makes it immediately distinguishable from pause_trigger and update_trigger without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when re-enabling a paused trigger after confirming with the user" gives a clear triggering condition plus a safety precondition. It does not explicitly name pause_trigger or other alternatives, but the paused-state framing makes the inverse relationship unambiguous.

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