mcp-airtable-query

Create records

create_records

Create up to ten records in a single Airtable request. Specify base ID, table, and record fields to bulk add data efficiently.

Instructions

Create up to ten records in one Airtable request.

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_records"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`data`	No
`error`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate a non-read-only, non-idempotent mutation. The description adds valuable context about batching (up to ten records per request), which is not provided by annotations or schema. It is consistent with annotations and does not omit critical safety information beyond what annotations cover.

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 a single sentence of 12 words, front-loaded with the action verb. Every word earns its place; it is highly concise and free of redundancy.

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

Completeness3/5

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

While the tool has a clear purpose and an output schema exists, the description omits important behavioral details such as the effect of 'typecast' or any error handling. The batching limit is noted, but for a create operation with four parameters, the description is somewhat underspecified. It is minimally viable but has room for improvement.

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%, so the description must compensate for explaining parameters. It only implies the 'records' parameter via 'up to ten records' but does not explain 'baseId', 'table', or especially 'typecast', which is a non-obvious Airtable concept. The schema provides names and types, but the description adds no extra meaning.

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 states a specific verb ('Create') and resource ('records in Airtable'), and adds a clear scope constraint ('up to ten') and batching behavior ('in one request'). It clearly distinguishes from siblings like update_records, delete_records, and list_records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool: for creating multiple records in a single request. It effectively differentiates from updating or deleting by naming 'Create'. It lacks explicit exclusions or alternative tool names, but the context is clear enough for basic selection.

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

Deploy Server