Skip to main content
Glama
onimsha

Airtable OAuth MCP Server

by onimsha

delete_records

Remove multiple records from an Airtable base using the Airtable OAuth MCP Server to manage data by specifying base, table, and record IDs.

Instructions

Delete multiple records

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe Airtable base ID
table_idYesThe table ID or name
record_idsYesList of record IDs to delete

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for delete_records. Registers the tool with FastMCP and implements the logic by calling AirtableClient.delete_records after authentication.
    @self.mcp.tool(description="Delete multiple records")
    async def delete_records(
        base_id: Annotated[str, Field(description="The Airtable base ID")],
        table_id: Annotated[str, Field(description="The table ID or name")],
        record_ids: Annotated[
            list[str], Field(description="List of record IDs to delete")
        ],
    ) -> list[str]:
        """Delete multiple records from a table."""
        client = await self._get_authenticated_client()
    
        deleted_ids = await client.delete_records(
            base_id,
            table_id,
            record_ids,
        )
    
        return deleted_ids
  • AirtableClient.delete_records method: makes DELETE request to Airtable API with record_ids, parses DeleteRecordsResponse, returns list of deleted IDs.
    async def delete_records(
        self,
        base_id: str,
        table_id: str,
        record_ids: list[str],
    ) -> list[str]:
        """Delete records from a table.
    
        Args:
            base_id: The Airtable base ID
            table_id: The table ID or name
            record_ids: List of record IDs to delete
    
        Returns:
            List of deleted record IDs
        """
        logger.info(f"Deleting {len(record_ids)} records from {base_id}/{table_id}")
    
        params = {"records[]": record_ids}
    
        response = await self._make_request(
            "DELETE",
            f"/v0/{base_id}/{table_id}",
            params=params,
            response_model=DeleteRecordsResponse,
        )
    
        return [record["id"] for record in response.records]
  • Pydantic schema/model for delete_records tool input arguments (base_id, table_id, record_ids).
    class DeleteRecordsArgs(BaseArgs):
        """Arguments for delete_records tool."""
    
        base_id: str = Field(description="The Airtable base ID")
        table_id: str = Field(description="The table ID or name")
        record_ids: list[str] = Field(description="List of record IDs to delete")
  • Pydantic model for Airtable delete records API response.
    class DeleteRecordsResponse(BaseModel):
        """Response from deleting records."""
    
        records: list[dict[str, Any]]
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action is deletion, implying a destructive mutation, but doesn't disclose behavioral traits like whether deletions are permanent, require specific permissions, have rate limits, or what happens on partial failures. This is inadequate for a destructive tool with zero annotation coverage.

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 extremely concise with a single sentence ('Delete multiple records'), front-loaded and zero waste. Every word earns its place by directly stating the tool's purpose without unnecessary elaboration.

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 this is a destructive mutation tool with no annotations, 100% schema coverage, and an output schema exists, the description is incomplete. It fails to address critical context like safety warnings, error handling, or output expectations, leaving gaps despite structured data covering parameters and outputs.

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 three parameters (base_id, table_id, record_ids) with descriptions. The description adds no additional meaning beyond what the schema provides, such as format details or usage examples, meeting the baseline for high coverage.

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 clearly states the action ('Delete') and resource ('multiple records'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'update_records' or 'create_records' beyond the deletion action, missing explicit sibling differentiation.

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' for modification or 'list_records' for viewing. The description lacks context about prerequisites, such as needing existing records to delete, or exclusions like when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/onimsha/airtable-mcp-server-oauth'

If you have feedback or need assistance with the MCP directory API, please join our Discord server