Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Trigger Automation

coda_trigger_automation

Trigger a Coda automation rule by providing its doc and rule IDs, with an optional JSON payload. Returns a request ID for tracking.

Instructions

Trigger a Coda automation rule.

Fires the specified automation rule, optionally passing a JSON payload. The automation must have an API-triggerable event type. The payload schema depends on the automation's configuration. Returns a requestId for tracking. The rule_id can be found in the automation's settings in the Coda UI.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the automation
payloadNoOptional JSON payload to pass to the automation
rule_idYesThe automation rule ID to trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare write (readOnlyHint=false) and open-world effects, so the safety profile is already covered. The description adds useful behavior: firing a rule, optional payload dependence, and a requestId return for tracking. It stops short of permission/auth or failure-mode detail.

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?

Front-loaded with the action, then five short lines covering prerequisite, payload variance, return value, and rule_id location. No filler or redundancy.

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 3-param mutation with no output schema, the description notes the requestId return and the API-triggerable prerequisite, which compensates for the missing output schema. It leaves auth/permission and error handling unstated, but annotations cover the main safety profile.

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 baseline is 3; the description adds that rule_id is found in automation settings and that payload shape depends on the target automation, which is meaningfully beyond schema text. Still, payload content itself remains opaque.

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 specific verb 'Trigger' and resource 'Coda automation rule' make the core action unambiguous, and the required doc_id/rule_id context is clear. However, the description does not differentiate this from the sibling coda_push_button, which may also initiate automations, so it falls short of the highest bar.

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

Usage Guidelines3/5

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

Gives a prerequisite ('must have an API-triggerable event type') and tells where to find rule_id, which helps invocation. But it does not say when to choose this over coda_push_button or other trigger mechanisms, nor when not to use it.

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