Skip to main content
Glama

list_triggers

Read-onlyIdempotent

List the triggers in this workspace: each watches one app for one kind of change and hands what it finds to the playbooks that use it. Use before creating one, to reuse an existing trigger when it already fits. Each says if it is published, whether a publish still needs a test, which playbooks use it, when it runs and what its last check did. Authoring details are in get_builder_guide topic "triggers".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_triggers"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeZoneNoThe user's IANA time zone, e.g. "Australia/Sydney". Pass it when you know it: times are read back on the user's own clock and never in UTC. Without one, a time of day is refused and no clock times are shown.

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 cover the safety profile (readOnlyHint, idempotentHint), and the description adds genuinely new context: each row reports published state, whether a publish still needs a test, the using playbooks, schedule, and last check outcome. What is not covered is pagination or result-size behaviour, which matters for a workspace-wide listing.

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?

Four sentences, none wasted: purpose first, usage rule second, payload contents third, deeper docs pointer last. Information is front-loaded in the order an agent needs it.

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?

There is no output schema, yet the description compensates by enumerating the per-trigger fields an agent will receive, which is exactly the right use of description space here. Only pagination or result-count behaviour is unaddressed.

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 description coverage is 100% and the single parameter (timeZone) is fully documented in the schema, including the consequence of omitting it. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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?

States a specific verb and resource ("List the triggers in this workspace") and then defines the resource concretely: "each watches one app for one kind of change and hands what it finds to the playbooks that use it." That definition separates it cleanly from list_playbooks, list_integrations, and the other list_* siblings.

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 before creating one, to reuse an existing trigger when it already fits" gives an explicit triggering condition tied to create_trigger, and it routes authoring questions to get_builder_guide topic "triggers". It stops short of stating exclusions or when not to list, so it is clear context rather than a full decision rule.

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