Airtable MCP Server

upsert

Create or update Airtable records by matching on chosen fields to merge new data into existing rows and prevent duplicates.

Instructions

Upsert Airtable records using performUpsert.fieldsToMergeOn.

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>",
      "performUpsert": "<performUpsert>"
    },
    "name": "upsert"
  }
}

Input Schema

Name	Required	Default
`table`	Yes
`baseId`	Yes
`dryRun`	No
`records`	Yes
`typecast`	No
`performUpsert`	Yes
`idempotencyKey`	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

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about mutation effects, permissions/scopes required, rate limits, or how conflicts are resolved by default. The mention of merging on fields does hint that existing records may be updated rather than duplicated, which is the only behavioral signal present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler, which is structurally clean. But its brevity comes at the cost of under-specification rather than genuine economy, given 8 parameters and nested objects.

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?

An output schema exists, so return values need not be explained, but for a multi-parameter write tool with nested records and no annotations the description is far too thin. The dry-run escape hatch and conflict-resolution behavior are the most important omissions for safe invocation.

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, and the description explains only performUpsert.fieldsToMergeOn. Critical controls such as dryRun, typecast, idempotencyKey, and the conflictStrategy enum (fail_on_conflict vs server_merge vs client_merge) are left entirely undocumented, forcing the agent to guess at semantics from names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (upsert) and resource (Airtable records) and names the merge mechanism (performUpsert.fieldsToMergeOn). However, it never distinguishes this tool from the sibling 'create' and 'update' tools, which is exactly the distinction an agent needs for an upsert operation.

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?

There is no guidance on when to choose upsert over create or update, no prerequisites (e.g. the merge fields must exist), and no mention of when not to use it. The single clause about fieldsToMergeOn implies matching semantics but gives no decision criteria.

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

Deploy Server