Airtable MCP Server

create

Adds new records to an Airtable base after a dry-run preview confirms changes, so you can validate updates before writing.

Instructions

Create 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": "create"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes
`baseId`	Yes
`dryRun`	No
`records`	Yes
`typecast`	No
`idempotencyKey`	No

Output Schema

Name	Required	Description	Default
`diff`	Yes
`dryRun`	Yes
`records`	No
`warnings`	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?

No annotations are supplied, so the description carries the burden of behavioral disclosure. It does surface a non-obvious prerequisite (diff-before-write via dryRun), which is valuable, but it omits permissions, idempotency behavior, typecast semantics, and response characteristics.

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 single sentence is front-loaded with the core action and the prerequisite, with no wasted words. It is slightly terse to the point of ambiguity ('diff-before-write'), but structurally efficient.

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?

For a six-parameter mutation tool with zero schema description coverage and no annotations, one sentence is insufficient. An output schema obviates documenting return values, but the input parameters and behavioral constraints remain largely unexplained.

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 six parameters. The description only indirectly explains 'dryRun'; it says nothing about 'typecast', 'idempotencyKey', or the shape of 'records' and 'fields', leaving most parameter semantics undocumented.

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 description states a specific verb and resource ('Create Airtable records'), which is clearly distinct from sibling mutators like 'update' and 'upsert'. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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?

It gives one concrete procedural rule: a dryRun must precede the write. That is useful, but there is no guidance on when to choose 'create' over sibling tools such as 'upsert' or 'update', and no mention of constraints on batch size or failure handling.

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

Deploy Server