Skip to main content
Glama
Airtable MCP Server

Airtable MCP Server

Update Employee

updateEmployee

Update an existing employee record in Airtable by employee ID to keep name, department, designation, email, phone, joining date, and status current.

Instructions

Update an existing employee in 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": "<name>",
      "department": "<department>",
      "designation": "<designation>",
      "email": "<email>",
      "phone": "<phone>",
      "joiningDate": "<joiningDate>",
      "status": "<status>"
    },
    "name": "updateEmployee"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEmployee Name
emailYesEmail Address
phoneYesPhone Number
statusYesEmployee Status
departmentYesDepartment
employeeIdYesEmployee ID
designationYesDesignation
joiningDateYesJoining Date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, reversibility, or what happens to unspecified fields. Critically, with all 8 parameters required, the description never warns that this appears to be a full overwrite of the employee record rather than a partial edit.

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 single short sentence is front-loaded and free of padding. Its brevity reflects under-specification rather than tight editing, but there is no wasted wording.

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 mutation tool with 8 all-required parameters, no annotations, and no output schema, a one-line description is not enough. It omits overwrite semantics, the existence requirement, and any return or error information the agent would need to call it safely.

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 names and describes all 8 parameters, making 3 the baseline. The description adds no meaning beyond the schema, in particular no clarification of whether every field must be re-supplied or what units/formats are enforced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('Update') and resource ('employee'), but adds almost nothing beyond the title 'Update Employee' other than 'existing' and 'in Airtable'. It does not say what aspects are updated or whether this is a full-record replacement, leaving the agent to infer from the schema.

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?

There is no when-to-use guidance, no mention of siblings like createEmployee or deleteEmployee, and no stated prerequisites such as needing the employee to already exist. The only implied condition is that the employee must be 'existing'.

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