Airtable OAuth MCP Server

list_records

Retrieve records from an Airtable table, with options to filter by formula, sort, specify fields, or select a view.

Instructions

List records from a table with optional filtering

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": {
      "base_id": "<base_id>",
      "table_id": "<table_id>"
    },
    "name": "list_records"
  }
}

Input Schema

Name	Required	Description
`base_id`	Yes	The Airtable base ID
`table_id`	Yes	The table ID or name
`view`	No	View name or ID
`filter_by_formula`	No	Airtable formula for filtering
`sort`	No	Sort configuration - array of {field: string, direction: 'asc'\|'desc'}
`fields`	No	Specific fields to include (field name or array of field names)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description must disclose behaviors. It mentions 'optional filtering' but does not disclose pagination, rate limits, record limits, or ordering. For a listing tool, this lack of behavioral context is a significant gap.

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 appropriately concise at 8 words, front-loading the core purpose. However, it could include a brief note on pagination or differentiation from search_records without much expansion. Still, it avoids unnecessary detail.

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?

Given the complexity (6 parameters, sibling search_records tool), the description is incomplete. It does not mention pagination, record limit defaults, or how filtering compares to search_records. Output schema exists but description still needs to cover behavioral gaps.

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 baseline is 3. The description adds only 'with optional filtering', which hints at available filtering parameters but does not add meaning beyond the schema. Schema already fully describes all 6 parameters.

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

Purpose5/5

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

The description clearly states 'List records from a table with optional filtering', specifying the action (list) and resource (records from a table). It distinguishes from siblings like get_record (single record) and search_records (more advanced search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for listing records with optional filtering, but does not explicitly differentiate from sibling search_records or state when to use this over alternatives. No guidance on prerequisites or exclusions.

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

Deploy Server