Airtable OAuth MCP Server

delete_records

Delete multiple records from an Airtable base and table by providing a list of record IDs.

Instructions

Delete multiple records

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": {
      "base_id": "<base_id>",
      "table_id": "<table_id>",
      "record_ids": "<record_ids>"
    },
    "name": "delete_records"
  }
}

Input Schema

Name	Required	Description
`base_id`	Yes	The Airtable base ID
`table_id`	Yes	The table ID or name
`record_ids`	Yes	List of record IDs to delete

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It only states the action without disclosing effects like irreversibility, permission requirements, or whether the operation is atomic. The agent receives no safety or side-effect information beyond the obvious destructive hint.

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 description is very brief at only two words, which is efficient. However, it lacks structure or front-loading of key information like input requirements. It earns its place but could be more informative in the same length.

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?

Given the tool's destructive nature and lack of annotations, the description is insufficient. It does not explain return values (though output schema exists), constraints on record count, or any post-deletion behavior. The tool's complexity (3 required params) demands more context.

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 coverage is 100% with concise parameter descriptions. The description adds no additional meaning beyond what's in the schema; baseline 3 is appropriate as the schema does the heavy lifting.

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 'Delete multiple records' clearly states the action and resource, distinguishing it from siblings like create_records or list_records. However, it could be more specific by mentioning the target system (Airtable) as inferred from schema parameter descriptions.

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?

No guidance is provided on when to use this tool versus alternatives like update_records or delete single records. There are no conditions or exclusions mentioned, leaving the agent without context for appropriate use.

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

Deploy Server