Skip to main content
Glama

Coline

Change a sheet automation

update_sheet_automation
Idempotent

Renames, turns on or off, or changes a sheet automation's trigger, conditions or steps.

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": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>",
      "automationId": "<automationId>"
    },
    "name": "update_sheet_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
actionsNo
enabledNo
sheetIdYesSheet id from search, fetch or create_sheet.
triggerNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conditionsNo
automationIdYes
conditionLogicNo

Output Schema

NameRequiredDescriptionDefault
automationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already disclose that this is a non-destructive, idempotent, non-read-only operation, lowering the disclosure burden. The description adds useful context by enumerating the mutable surfaces (name, enabled, trigger, conditions, steps), but it does not say whether updates are partial or full-replacement, nor whether permissions are required.

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?

The definition is a single tightly written sentence with no filler, and the most important mutable fields are front-loaded. Every clause contributes to telling the agent what can be changed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has nine parameters, nested oneOf objects, and a mutation surface, so the description is reasonably informative but incomplete. It omits partial-update semantics (whether omitted fields are preserved) and leaves conditionLogic and automationId undocumented anywhere, which matters for an update tool.

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 22%, so the description must compensate, and it does map several parameters semantically: 'renames' to name, 'turns on or off' to enabled, and 'trigger, conditions or steps' to trigger, conditions, and actions. However, it leaves conditionLogic and automationId unexplained, and the required workspace/sheetId are only covered by the schema itself.

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 uses a specific verb set (renames, turns on/off, changes) and a specific resource (a sheet automation), and names the changeable sub-resources (trigger, conditions, steps). It clearly conveys an update operation without explicitly distinguishing itself from create_sheet_automation or delete_sheet_automation.

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

Usage Guidelines2/5

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

The description implies use for modifying an existing automation but gives no explicit when-to-use guidance, prerequisites, or comparisons to sibling tools such as create_sheet_automation or delete_sheet_automation. An agent must infer that this is the mutation path for existing automations.

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