Airtable Full-Stack MCP

Overview Schema Source Related Servers Discussions Admin

airtable_manage_webhook

Set up real-time Airtable webhooks to trigger instant notifications on record or schema changes. Use to create, list, inspect payloads, or delete webhooks, enabling live syncs with external platforms.

Instructions

Manages real-time Airtable Webhooks for bidirectional integrations with external platforms (Tally, Fillout, Stripe, PayPal, Make, Zapier, or custom backends).

When to Use

When you need instant notifications when records or schema change in an Airtable base.
When configuring real-time sync pipelines to external data warehouses or webhook receivers.
When listing, inspecting recent transaction payloads, or tearing down obsolete webhooks.

When NOT to Use

Do NOT use this tool for batch data imports or record querying. Use 'airtable_batch_upsert' or 'airtable_query_records' instead.
Do NOT use this tool to write automation logic inside Airtable. Use 'airtable_generate_automation_script' instead.

Operational Disclosures

Side Effects: 'create' registers a persistent HTTP webhook endpoint on Airtable's infrastructure. 'delete' permanently revokes delivery to that endpoint.
Persistence: Webhooks persist on the base until explicitly deleted or until they expire after consecutive failed delivery attempts.
Auth Scopes: Requires a Personal Access Token with the 'webhook:manage' scope.
Rate Limits: Governed by Airtable's 5 req/sec API quota with automatic backoff retry.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Action to perform: 'create' registers a new webhook, 'list' returns all registered webhooks, 'delete' removes a webhook by ID, 'payloads' retrieves change events
`cursor`	No	Payload pagination cursor from a previous response (optional, used when action is 'payloads')
`base_id`	Yes	Airtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)
`webhook_id`	No	Airtable Webhook ID (starts with ach..., required when action is 'delete' or 'payloads')
`specification`	No	Optional granular event filter specification (e.g. watchDataInTables, fromSources: ['client', 'publicApi', 'formSubmission', 'automation'])
`notification_url`	No	Target HTTPS URL to receive POST notifications when changes occur (required when action is 'create')

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?

With no annotations provided, the description carries the full burden, and it delivers richly: it discloses side effects of create/delete, persistence and expiration behavior, required auth scopes, and rate limits. These are exactly the non-obvious behavioral traits an agent needs before invoking 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.

Conciseness5/5

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

The description is well-structured with clear headers and bullets. The first sentence states the tool's purpose immediately, and each subsequent section earns its place by adding operational or routing context without redundancy.

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 tool with four actions, six parameters, nested objects, and no output schema, the description covers the essential contextual gaps: side effects, persistence, auth, rate limits, and sibling routing. Combined with the fully documented input schema, an agent has enough to select and invoke this tool correctly.

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 all six parameters thoroughly. The description adds some nuance about action side effects and persistence, but it does not substantially extend parameter-level meaning beyond what the input schema provides.

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 clear verb and resource: 'Manages real-time Airtable Webhooks for bidirectional integrations.' It explicitly names the actions (create, list, delete, payloads) and distinguishes itself from sibling tools by calling out what it is not for, such as batch imports, queries, and automation scripts.

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 description has explicit 'When to Use' and 'When NOT to Use' sections with concrete alternatives, e.g., 'Use airtable_batch_upsert or airtable_query_records instead' and 'Use airtable_generate_automation_script instead.' This gives an agent unambiguous routing criteria.

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

Deploy Server