Airtable MCP Server

query

Retrieve Airtable records with formula filters, field selection, sorting, and pagination to get specific rows from a base table.

Instructions

Query Airtable records with filtering, sorting, and pagination.

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": {
      "baseId": "<baseId>",
      "table": "<table>"
    },
    "name": "query"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No
`sorts`	No
`table`	Yes
`baseId`	Yes
`fields`	No
`offset`	No
`pageSize`	No
`maxRecords`	No
`filterByFormula`	No
`returnFieldsByFieldId`	No

Output Schema

Name	Required	Description	Default
`offset`	No
`records`	Yes
`summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.7Nov 8, 2026

TDQS

C2.7/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 behavioral burden, and it only hints that pagination exists. It does not state that this is a read-only operation, how the offset token is obtained or reused, whether maxRecords truncates results silently, or what permissions/base access are required.

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?

One front-loaded sentence with no filler or repetition. It is efficient, though at this brevity it under-serves a 10-parameter tool rather than being genuinely optimal.

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?

The presence of an output schema means return values need not be explained, but for a 10-parameter query tool with zero schema descriptions and no annotations, the description is far too thin. Required identifiers, formula syntax, and pagination mechanics are all left undocumented.

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% across 10 parameters, so the description must compensate and does not. It gestures at filtering, sorting, and pagination but never mentions baseId/table (both required), view scoping, fields projection, or that filterByFormula expects Airtable formula syntax — the single most error-prone parameter.

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?

States a specific verb and resource ("Query Airtable records") and names the three capabilities (filtering, sorting, pagination). It is clear what the tool does, but it never distinguishes itself from siblings like describe or list_bases, so an agent must infer the boundary.

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 or when-not-to-use guidance and no named alternative among the sibling tools. The read-only intent is only implied by the word "query"; nothing tells an agent to prefer create/update/upsert for writes or describe for schema inspection.

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

Deploy Server