Skip to main content
Glama

update_trigger

Idempotent

Updates only the trigger fields you supply; because trigger_config replaces the full configuration, read the trigger first and include every setting you want to retain.

Instructions

Update only supplied trigger fields. trigger_config replaces the entire configuration; read get_trigger first and include all settings to retain.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew name
api_key_idNoNew API key for execution
trigger_idYesUUID of the trigger to update
descriptionNoNew description
trigger_configNoNew trigger configuration in the format used by create_trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.4
    • changedInput schema / properties / api_key_id / description
      Previous value: -"Nova API Key para execução"New value: +"New API key for execution"
    • changedInput schema / properties / description / description
      Previous value: -"Nova descrição"New value: +"New description"
    • changedInput schema / properties / name / description
      Previous value: -"Novo nome"New value: +"New name"
    • changedInput schema / properties / trigger_config / description
      Previous value: -"Nova configuração do trigger (mesma estrutura por tipo de create_trigger)"New value: +"New trigger configuration in the format used by create_trigger"
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger a atualizar"New value: +"UUID of the trigger to update"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish non-readonly, non-destructive, idempotent behavior. The description adds the critical disclosure that trigger_config replaces the entire configuration, which is behavior beyond the annotations and helps the agent avoid clobbering settings. It does not cover permissions or response behavior, so it is strong but not 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?

Two short sentences, front-loaded with the key partial-update rule and immediately followed by the critical replacement caveat. Every sentence earns its place.

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-parameter update tool with a nested object, full schema coverage, and annotations, the description covers the main behavioral risk. It does not describe the return value, but no output schema exists and the essential call guidance is present.

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 the parameter schema already defines all five fields. The description adds meaningful semantics for trigger_config specifically: it replaces the entire configuration and requires reading get_trigger first. Other parameters are left to the schema, which is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Update ... trigger fields') and clarifies the partial-update scope with 'only supplied trigger fields.' It distinguishes itself from a full replacement, though it does not explicitly differentiate from siblings like toggle_trigger or create_trigger beyond referencing get_trigger.

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?

It gives explicit workflow guidance: read get_trigger first and include all settings to retain. This is clear usage context for the dangerous parameter, but it does not state when not to use this tool or name an alternative operation such as toggle_trigger.

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

Deploy Server

Other Tools