Skip to main content
Glama
Airtable MCP Server

Airtable MCP Server

Create Employee

createEmployee

Creates a new employee record in Airtable from supplied ID, name, department, designation, email, phone, joining date, and status, enabling AI clients to add structured employee data.

Instructions

Create a new 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": "createEmployee"
  }
}

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.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 disclosure burden and does not meet it: it never says what happens on a duplicate employeeId, whether all eight fields are mandatory, whether the record lands in a specific base/table, or what the tool returns. Only the bare mutation intent is conveyed.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity is achieved by omitting information rather than by tightly compressing it.

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 an eight-required-parameter mutation with no annotations and no output schema, the description should cover failure modes, uniqueness requirements, and the result shape. It covers none of these, leaving the agent under-informed about a consequential write.

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% and every field carries its own description, so the schema already does the parameter work. The description adds no format or constraint details beyond it, which is the expected baseline here.

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 states a specific verb and resource ("Create a new employee") and names the target system (Airtable), which is unambiguous against the read/delete/update siblings. It stops short of explicitly differentiating itself from updateEmployee or advancedEmployeeSearch, so it is clear but not fully disambiguating.

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 guidance on when to use this versus updateEmployee or advancedEmployeeSearch, and no prerequisites such as whether the employee must not already exist. The agent must infer that this is the write path for brand-new records.

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