Skip to main content
Glama

update_trigger

Modify an existing automation trigger in place by replacing its sources, filters, condition, emit settings, cooldown, or project without creating a new trigger.

Instructions

Edit an EXISTING trigger in place: replace its sources, filters, key_field, condition, emit and cooldown, and move it to another project when given. Create new triggers with create_trigger(); this only updates one that already exists (renaming isn't supported, so keep name the same). description left out keeps the current one, "" clears it. See create_trigger for the shapes.

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": {
      "name": "<name>",
      "sources": "<sources>",
      "condition": "<condition>"
    },
    "name": "update_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
emitNo
nameYes
filtersNo
projectNo
sourcesYes
cooldownNo5m
conditionYes
key_fieldNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does it well: it discloses replace-not-merge semantics for sources/filters/key_field/condition/emit/cooldown, that an omitted `description` preserves the current value while "" clears it, that the trigger can be moved to another project, and that renaming is unsupported. It doesn't mention permission requirements or what happens to fields not listed, so it falls short of complete.

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?

Three tight sentences, front-loaded with the core scope claim, then the sibling routing, then edge-case semantics. Every clause carries information an agent needs; nothing is 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?

An output schema exists, so return values need not be explained, and the description covers the update semantics for a 9-parameter tool with nested objects. The residual gap is the nested-object shapes being outsourced to create_trigger and the absence of any auth or side-effect context for a mutation.

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 0%, so the description must compensate, and it does for most parameters: null-vs-empty semantics for `description`, `project` as a move target, and `name` as a non-renameable key. It defers the internal shapes of `emit`, `filters`, `condition`, and `key_field` to create_trigger, and says nothing about the `cooldown` default, leaving some structural meaning to inference.

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 ('Edit an EXISTING trigger in place') and enumerates the fields it touches: sources, filters, key_field, condition, emit, cooldown, project. It explicitly distinguishes itself from create_trigger(), so an agent can separate the two without inspecting either 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?

Gives explicit when-to-use guidance ('Create new triggers with create_trigger(); this only updates one that already exists') and a concrete constraint: renaming isn't supported, so keep `name` the same. The main alternative is named along with the condition that selects it.

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