Skip to main content
Glama
felores

Airtable MCP Server

by felores

list_records

Retrieve records from an Airtable table by specifying the base ID and table name, with optional limit on results.

Instructions

List records in a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base
table_nameYesName of the table
max_recordsNoMaximum number of records to return

Implementation Reference

  • The handler implementation for the 'list_records' tool. It destructures the input arguments, performs a GET request to the Airtable API to list records from the specified table (with optional maxRecords parameter), and returns the records as formatted JSON text content.
    case "list_records": {
      const { base_id, table_name, max_records } = request.params.arguments as {
        base_id: string;
        table_name: string;
        max_records?: number;
      };
      const response = await this.axiosInstance.get(`/${base_id}/${table_name}`, {
        params: max_records ? { maxRecords: max_records } : undefined,
      });
      return {
        content: [{
          type: "text",
          text: JSON.stringify(response.data.records, null, 2),
        }],
      };
    }
  • The input schema for the 'list_records' tool, defining the expected parameters: required base_id and table_name (strings), optional max_records (number). Used for validation in tool calls.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "ID of the base",
        },
        table_name: {
          type: "string",
          description: "Name of the table",
        },
        max_records: {
          type: "number",
          description: "Maximum number of records to return",
        },
      },
      required: ["base_id", "table_name"],
    },
  • src/index.ts:253-274 (registration)
    The registration of the 'list_records' tool in the list of available tools returned by ListToolsRequestSchema. Includes name, description, and input schema.
    {
      name: "list_records",
      description: "List records in a table",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_name: {
            type: "string",
            description: "Name of the table",
          },
          max_records: {
            type: "number",
            description: "Maximum number of records to return",
          },
        },
        required: ["base_id", "table_name"],
      },
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, pagination, or any side effects. The description assumes a straightforward list operation but leaves important details implicit.

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

Conciseness2/5

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

The description is extremely concise (4 words), but it is under-specified. Important information such as scope (all records vs filtered) and behavioral details are missing, making it insufficiently informative for the agent.

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 presence of sibling tools and no output schema or annotations, the description lacks completeness. It does not explain return format, pagination, or differentiation from similar tools, leaving agents with insufficient context to use the tool correctly.

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?

The input schema has 100% description coverage, so the baseline is 3. The description does not add any additional meaning beyond what is already in the schema. Parameters are adequately described in the schema, but the description offers no extra context.

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 clearly states the action (list) and resource (records in a table). It is specific enough for basic understanding, but does not differentiate from sibling tools like advanced_list_records, which may offer additional filtering options.

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?

No guidance is provided on when to use this tool versus alternatives such as advanced_list_records or search_records. The description lacks any context about appropriate use cases or exclusions.

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