Skip to main content
Glama
Airtable MCP Server

Airtable MCP Server

Delete Employee

deleteEmployee

Deletes a specific employee record from Airtable using employeeId so AI clients can remove outdated or incorrect employee data from a base.

Instructions

Delete an employee from Airtable

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": {
      "employeeId": "<employeeId>"
    },
    "name": "deleteEmployee"
  }
}

Input Schema

NameRequiredDescriptionDefault
employeeIdYesEmployee ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 behavioral burden. It states the tool deletes an employee but does not disclose whether deletion is permanent, what permissions are required, what happens to related records, or what the response contains.

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 a single front-loaded sentence with no wasted wording. Its brevity is appropriate for conciseness, though the same brevity contributes to missing usage and behavioral context.

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?

For a destructive delete operation with no annotations and no output schema, the description is incomplete. It should at least clarify permanence and any confirmation or permission requirements so an agent can invoke it responsibly.

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 single employeeId parameter is already documented in the schema. The description adds no additional meaning about identifier format or constraints, which is acceptable given the schema coverage but not value-adding.

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 uses a specific verb (Delete) and resource (an employee from Airtable), making the operation clear. It does not explicitly distinguish itself from siblings like updateEmployee, but the destructive verb makes the distinction reasonably obvious.

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 gives no when-to-use guidance, no alternatives, and no caution about when not to use this tool. For a destructive operation with sibling updateEmployee and createEmployee, some routing or prerequisite context would be expected.

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