Skip to main content
Glama

create_trigger

Create a trigger: it starts unpublished (nothing runs) and will check every 5 minutes once published. Reuse an existing one when it fits (see list_triggers). scope is what every playbook on it shares, in plain words; fetch is the code that reads the app (contract in get_builder_guide topic "triggers"). After creating, test_trigger then publish_trigger.

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": {
      "integration": "<integration>",
      "event": "<event>",
      "scope": "<scope>",
      "fetch": "<fetch>",
      "name": "<name>"
    },
    "name": "create_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA short name a person would recognise, e.g. "Candidate tickets".
eventYesThe kind of change it watches for, e.g. "ticket.updated".
fetchYesThe fetch code: a module exporting `async function fetch({ cursor }, ctx)` and, where the app can read by time, `startFrom`.
scopeYesWhat every playbook on this trigger shares, in plain words, e.g. "candidate support form, open tickets".
integrationYesThe app it watches, as list_integrations names it, e.g. "zendesk".

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description contributes the non-obvious behavior that the trigger is inert until published and that its polling cadence is 5 minutes. It does not cover permissions, what happens on a failing fetch, or whether duplicate triggers are allowed, so it falls short of fully rich behavioral disclosure.

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?

Front-loads creation and the unpublished-start behavior, then covers reuse, parameter meaning, and the follow-up sequence in three tight sentences. Every clause carries information an agent needs to act correctly, with no filler.

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 five-required-parameter creation tool with no output schema, the description supplies lifecycle behavior, an alternative, and a pointer to the fetch-code contract. The one remaining gap is that it never says what the call returns or how the newly created trigger is identified for the subsequent test_trigger/publish_trigger steps.

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%, so all five parameters are already documented at the field level, making 3 the baseline. The description does add interpretive value for `scope` ('what every playbook on it shares, in plain words') and for `fetch` (code that reads the app, with the contract in get_builder_guide topic 'triggers'), but this largely echoes the schema wording.

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 ('Create a trigger') and immediately adds its distinguishing lifecycle property: it starts unpublished so nothing runs, then polls every 5 minutes once published. This separates it cleanly from update_trigger, publish_trigger, and the other trigger siblings without the agent needing another schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent away from creation when an existing trigger fits ('Reuse an existing one when it fits (see list_triggers)') and gives the mandatory follow-up sequence ('test_trigger then publish_trigger'). Both the alternative and the downstream workflow are named, leaving little to inference.

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