SeaTable MCP

Official

Overview Schema Source Related Servers Discussions Admin

update_rows

DestructiveIdempotent

Batch update multiple rows in a specified SeaTable table. Provide an array of row IDs and new column values. Rejects unknown columns. Does not modify link, file, or image columns.

Instructions

Batch update rows. Rejects unknown columns. Link and file/image columns cannot be modified here — use link_rows/unlink_rows and upload_file instead.

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": {
      "table": "<table>",
      "updates": "<updates>"
    },
    "name": "update_rows"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes	Target table name
`updates`	Yes	Array of updates, each with row_id and values

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.2Apr 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate destructiveHint=true and idempotentHint=true, which the description does not contradict. The description adds behavioral context: 'Rejects unknown columns' and limitations on certain column types. With annotations already covering safety, the description effectively adds value beyond annotations.

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 description is extremely concise: three short sentences covering purpose, constraints, and alternatives. No wasted words, information is front-loaded.

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?

Given the tool's complexity, available schema, and annotations, the description covers the essential aspects: purpose, constraints on column types, and sibling tool alternatives. It lacks details about return values or error handling, but the tool has no output schema and is relatively straightforward. A minor gap for completeness.

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 coverage is 100%, so the schema already documents both parameters thoroughly. The description does not add additional parameter details beyond what the schema provides, so a baseline of 3 is appropriate.

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: 'Batch update rows' (specific verb+resource). It also explicitly distinguishes itself from siblings by noting that link/file/image columns cannot be modified here and directing to link_rows/unlink_rows and upload_file instead, which differentiates it from related tools.

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?

The description provides explicit guidance on when not to use this tool: 'Link and file/image columns cannot be modified here — use link_rows/unlink_rows and upload_file instead.' This gives clear alternatives and usage boundaries.

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