Airtable Full-Stack MCP

Overview Schema Source Related Servers Discussions Admin

airtable_modify_schema

Modify an existing Airtable schema by adding fields, renaming tables or fields, and updating descriptions via the Metadata API.

Instructions

Evolves an existing Airtable schema: adds new custom fields to an existing table, updates field names/descriptions, or updates table names/descriptions via Metadata API.

When to Use

When adding a new column/field to an existing table without recreating the whole base.
When renaming a field or table to improve operational clarity.
When updating field or table documentation descriptions.

When NOT to Use

Do NOT use this tool to initialize an entire new base schema with multiple tables. Use 'airtable_create_base_schema' instead.
Do NOT use this tool to update row values or cell data. Use 'airtable_manage_records' instead.

Operational Disclosures

Side Effects: 'create_field' adds a persistent new column. 'update_field' and 'update_table' mutate existing schema metadata.
Persistence: Schema modifications are immediately persistent across all base views and interfaces.
Auth Scopes: Requires Personal Access Token with 'schema.bases:write' scope.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Action to perform: 'create_field' adds a new column, 'update_field' modifies field metadata, 'update_table' modifies table metadata
`base_id`	Yes	Airtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)
`field_id`	No	Target Field ID (starts with fld, required when action is 'update_field')
`field_config`	No	Field configuration object (required when action is 'create_field')
`update_config`	No	Metadata updates to apply (required when action is 'update_field' or 'update_table')
`table_id_or_name`	Yes	Target Table Name or Table ID (starts with tbl)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.1Sep 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It explicitly states side effects per action, persistence across views and interfaces, and required auth scope ('schema.bases:write'). This is substantial behavioral disclosure beyond what the schema offers.

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 well-structured with clear headers and bullet lists. The opening sentence summarizes the tool, followed by usage guidance, exclusions, and disclosures. Every sentence earns its place; there is no redundant or vague filler.

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

Completeness5/5

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

For a mutation tool with a rich input schema and no annotations, the description covers purpose, when to use, when not to use, side effects, persistence, and auth. It gives an agent everything needed to decide whether and how to invoke it correctly, leaving parameter details to the schema.

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?

Schema description coverage is 100%, so the schema already documents every parameter and its constraints. The description adds operational context for actions but does not introduce new parameter-level semantics, making the baseline 3 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 opens with a specific verb and resource: it 'evolves an existing Airtable schema' and enumerates exact operations (adds fields, updates field/table names and descriptions). It also differentiates itself from sibling tools by explicitly naming what it is not for (creating new base schemas, updating row values).

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 'When to Use' section lists concrete triggers (adding a column, renaming, updating descriptions), and the 'When NOT to Use' section names the correct alternatives ('airtable_create_base_schema' and 'airtable_manage_records'). This gives an agent clear routing guidance with no ambiguity.

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

Deploy Server