Airtable MCP Server

update

Modify Airtable records by applying field changes to specified record IDs; use a dry-run diff first to preview changes and avoid unintended writes.

Instructions

Update Airtable records (requires diff-before-write via dryRun first).

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": {
      "baseId": "<baseId>",
      "table": "<table>",
      "records": "<records>"
    },
    "name": "update"
  }
}

Input Schema

Name	Required	Default
`table`	Yes
`baseId`	Yes
`dryRun`	No
`records`	Yes
`typecast`	No
`idempotencyKey`	No
`ifUnchangedHash`	No
`conflictStrategy`	No	fail_on_conflict

Output Schema

Name	Required	Description	Default
`diff`	Yes
`dryRun`	Yes
`records`	No
`conflicts`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.7Nov 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavioral trait: a mandatory dry-run/diff step before writing. It says nothing about whether the update is partial-merge or replace, how conflictStrategy behaves, or what happens when ifUnchangedHash mismatches — all significant for a mutation tool.

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?

A single front-loaded sentence with no filler, and the critical dry-run constraint is placed where the agent will see it. It is arguably undersized for an 8-parameter mutation tool, but nothing is redundant.

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?

This is a complex write tool with 8 parameters, no annotations, and zero schema descriptions; the description covers only one of those parameters. The output schema exists, so return values need not be explained, but the input-side and conflict-handling behavior is far too thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description must compensate and largely does not. It only alludes to dryRun; idempotencyKey, ifUnchangedHash, typecast, and the conflictStrategy enum values are left entirely unexplained.

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?

States a specific verb and resource ("Update Airtable records"), so the agent knows this is a record mutation against Airtable. It does not distinguish itself from the sibling 'upsert' or 'create', which are the most likely confusions for a write tool.

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?

The parenthetical "requires diff-before-write via dryRun first" gives a concrete workflow prerequisite, which is real usage guidance. However, there is no guidance on when to choose this over upsert or create, and no exclusions or preconditions beyond the dry-run note.

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

Deploy Server