Skip to main content
Glama

publish_trigger

Destructive

Make the trigger's working copy live: it starts checking the app on its schedule and handing items to the playbooks that use it. Refused unless its last test was of exactly this working copy and passed. A trigger can be shared by several playbooks, so confirm with the user what goes live before calling this. Pass definitionHash from get_trigger as expectedDefinitionHash so publish is refused if the trigger changed while deciding. cursor says where it carries on from: { to: "keep" } (default), { to: "now" }, { to: "hoursBack", hours } (up to 30 days) or { to: "time", time }. Anything but keep looks at older items again: what a playbook already handled won't run twice, but what it hasn't handled yet will, so confirm first and pass lookBackTarget from the same get_trigger as expectedLookBackTarget for hoursBack or time. A playbook can only be published once the triggers it uses are published.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoWhere it carries on from. Omit to keep where it is.
triggerIdYesThe trigger's id, from list_triggers or create_trigger.
expectedDefinitionHashYesThe `definitionHash` from the get_trigger you showed the user, taken before you asked them.
expectedLookBackTargetNoFor hoursBack or time: the `lookBackTarget` from the get_trigger you showed the user.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is destructive and open-world; the description adds the real behavioral stakes: which playbooks are affected, the refusal-on-stale-test rule, optimistic-concurrency refusal via expectedDefinitionHash, and exactly what re-processing happens with non-keep cursors. That is substantially more than the annotation profile provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the effect, then preconditions, then cursor semantics; every sentence carries operational meaning. It is dense and the cursor sentence is long, which slightly hurts scannability for a destructive tool, but nothing is filler.

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 destructive, open-world mutation with no output schema and a nested object parameter, the description covers preconditions, cross-playbook blast radius, concurrency refusal, and cursor look-back semantics. An agent has enough to call it safely without further discovery.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so this is already above baseline, but the description still adds intent: expectedDefinitionHash is a concurrency guard captured before asking the user, and cursor values are explained in terms of which items get reprocessed, including the already-handled idempotency caveat. Only gap is it doesn't restate the 30-day/time-format bounds, which the schema covers anyway.

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?

Opens with a concrete verb+resource+effect: 'Make the trigger's working copy live', then spells out the consequence (starts checking the app on schedule and handing items to playbooks). It also separates itself from publish_playbook by stating the ordering dependency between the two.

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?

Gives explicit preconditions ('Refused unless its last test was of exactly this working copy and passed'), an explicit user-confirmation step because a trigger can be shared by several playbooks, and directs the agent to get_trigger for the hash inputs. When-not conditions and the sibling relationship to publish_playbook are both stated.

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