Coda MCP Server

coda_upsert_rows

Insert or update rows in a Coda table by specifying key columns for matching.

Instructions

Insert or upsert rows into a table

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": {
      "docId": "<docId>",
      "tableIdOrName": "<tableIdOrName>",
      "rows": "<rows>"
    },
    "name": "coda_upsert_rows"
  }
}

Input Schema

Name	Required	Description
`docId`	Yes	The ID of the document
`tableIdOrName`	Yes	The ID or name of the table
`rows`	Yes	JSON string of rows to upsert, e.g. [{"cells": [{"column": "Name", "value": "Alice"}, {"column": "Age", "value": 30}]}]
`keyColumns`	No	JSON string of column IDs or names to use as upsert keys, e.g. ["Name"] - optional

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.1May 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description only states the action ('upsert'), but does not disclose behavioral details such as idempotency, conflict resolution, error handling, or required permissions. Since no annotations are provided, the description carries full burden but falls short.

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?

The description is extremely concise—one sentence—which is efficient for a straightforward operation. However, it may be too minimal for a complex tool with multiple optional parameters. The information is front-loaded but lacks necessary context.

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

Completeness2/5

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

Given the tool has 4 parameters, no output schema, and no annotations, the description is insufficient. It omits key behavioral details (e.g., how upsert keys work, when rows are inserted vs updated). For a data-modifying tool, more context is needed to ensure correct usage.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds an example for 'rows' parameter, which is helpful but not essential. Baseline is 3 because schema already documents parameters adequately. The tool description does not provide additional parameter-level guidance beyond the schema.

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 clearly states the tool's purpose: 'Insert or upsert rows into a table'. It uses a specific verb ('upsert') and resource ('rows into a table'), and it implies distinction from sibling tools like coda_update_row (singular row) and coda_insert_rows (if present). The purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives. It does not explain scenarios for choice between upsert and separate insert/update operations, nor does it mention prerequisites like keyColumns. Siblings include update and delete tools, but no comparative context is provided.

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