Skip to main content
Glama
felores

Airtable MCP Server

by felores

delete_record

Remove a specific record from an Airtable table by providing the base ID, table name, and record ID to delete unwanted data entries.

Instructions

Delete a record from a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base
table_nameYesName of the table
record_idYesID of the record to delete

Implementation Reference

  • The handler for the 'delete_record' tool. It extracts base_id, table_name, and record_id from arguments, makes a DELETE request to the Airtable API endpoint for that record, and returns the response data.
    case "delete_record": {
      const { base_id, table_name, record_id } = request.params.arguments as {
        base_id: string;
        table_name: string;
        record_id: string;
      };
      const response = await this.axiosInstance.delete(
        `/${base_id}/${table_name}/${record_id}`
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(response.data, null, 2),
        }],
      };
    }
  • src/index.ts:323-344 (registration)
    Registration of the 'delete_record' tool in the listTools response, including its name, description, and input schema.
    {
      name: "delete_record",
      description: "Delete a record from a table",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_name: {
            type: "string",
            description: "Name of the table",
          },
          record_id: {
            type: "string",
            description: "ID of the record to delete",
          },
        },
        required: ["base_id", "table_name", "record_id"],
      },
    },
  • Input schema definition for the 'delete_record' tool.
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_name: {
            type: "string",
            description: "Name of the table",
          },
          record_id: {
            type: "string",
            description: "ID of the record to delete",
          },
        },
        required: ["base_id", "table_name", "record_id"],
      },
    },
Behavior2/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 of behavioral disclosure. It states the action is 'Delete,' implying a destructive mutation, but does not address critical aspects like whether deletion is permanent, requires specific permissions, has side effects, or provides confirmation. This is a significant gap for a destructive operation.

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, direct sentence with zero wasted words. It is appropriately sized and front-loaded, efficiently conveying the core action without unnecessary details.

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 or output schema, the description is incomplete. It fails to address behavioral risks, return values, or error conditions, leaving the agent with insufficient information for safe and effective use.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (base_id, table_name, record_id). The description does not add any meaning beyond the schema, such as explaining relationships between parameters or providing examples. Baseline 3 is appropriate as the schema handles 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 clearly states the action ('Delete') and resource ('a record from a table'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like 'update_record' or 'create_record' beyond the verb, which would require more specificity about what distinguishes deletion from other operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an existing record, or compare it to siblings like 'update_record' for modifications. This lack of context leaves the agent without clear usage instructions.

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/felores/airtable-mcp'

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