Skip to main content
Glama

update_trigger

Idempotent

Change the name or any part of a trigger's working copy (app, event, scope, fetch code); what is left out stays as it is. Nothing that runs changes until it is published, and the last test no longer counts: test again first. A published trigger can't switch to another app or event; create a new one.

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": "update_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
eventNo
fetchNo
scopeNo
triggerIdYesThe trigger's id, from list_triggers or create_trigger.
integrationNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the important behavioral traits: edits land in a draft that does not take effect until published, prior test results are invalidated, and some fields are immutable once published. It does not cover permission/auth requirements or what the response contains, which keeps it short of a 5.

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?

Three dense sentences, front-loaded with the mutation scope before moving to side effects and the immutability caveat. Every sentence carries information, though the domain jargon ('working copy', 'the last test no longer counts') is compacted tightly enough to require a second read.

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 mutation tool with no output schema and sparse schema documentation, the description covers the draft/publish lifecycle, test invalidation, and field immutability, which are the main ways an agent could misuse it. The remaining gap is the unexplained 'integration' parameter and lack of any return-value or error expectation.

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 only 17% (triggerId alone is documented), so the description has to carry the parameter burden and does add meaning for name, event, scope, and fetch code. However it never explains the 'integration' parameter explicitly (the 'app' wording is only implied in the immutability sentence), nor any format or length constraints for fetch code, leaving one of six parameters effectively unexplained.

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?

The description opens with a specific verb and scoped resource ('Change the name or any part of a trigger's working copy') and then enumerates the mutable fields (app, event, scope, fetch code). It is clearly distinguishable from publish_trigger, test_trigger, and create_trigger because it is explicitly framed as editing a draft working copy.

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?

It gives an explicit partial-update rule ('what is left out stays as it is'), a precondition workflow ('the last test no longer counts: test again first'), and an exclusion with the alternative spelled out ('A published trigger can't switch to another app or event; create a new one'). The agent knows both when to call this and when to fall back to create_trigger.

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