Skip to main content
Glama
Airtable MCP Server

Airtable MCP Server

Advanced Employee Search

advancedEmployeeSearch

Search employee records by name, department, status, designation, or employee ID to locate specific staff in Airtable.

Instructions

Search employees using different fields

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": {
      "searchBy": "<searchBy>",
      "searchValue": "<searchValue>"
    },
    "name": "advancedEmployeeSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchByYes
searchValueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden. It never states that this is a read-only operation, whether matching is exact or substring, case sensitivity, result caps, or pagination — all of which materially affect how an agent calls it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but the brevity comes from under-specification rather than precision. It is front-loaded adequately but says almost nothing.

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 two-parameter required-input search tool with no annotations and no output schema, the definition should describe matching behavior and result characteristics. Instead the agent is left to guess at semantics that determine whether the call succeeds or returns nothing useful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the enum values (Name, Department, Status, Designation, Employee ID) are unlabeled as to expected value formats. The phrase "different fields" hints that searchBy selects the field but adds no meaning about how searchValue must be formatted per field.

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?

"Search employees" names a verb and resource, but "using different fields" is vague filler rather than a statement of scope or capability. It is distinguishable from siblings like createEmployee/deleteEmployee by the search verb alone, but nothing in the text sharpens that distinction.

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 search versus the dashboard or any other retrieval path, and no stated preconditions. The agent must infer everything about appropriateness from the tool name.

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