Airtable MCP Server

list_bases

Retrieve all accessible Airtable bases to view available workspaces and their contents for data management.

Instructions

List all accessible Airtable bases

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:399-407 (handler)

Handler for the 'list_bases' tool: fetches all accessible Airtable bases via API and returns JSON stringified response.

case "list_bases": {
  const response = await this.axiosInstance.get("/meta/bases");
  return {
    content: [{
      type: "text",
      text: JSON.stringify(response.data.bases, null, 2),
    }],
  };
}

src/index.ts:77-85 (registration)

Tool registration including name, description, and input schema (empty object, no params required).

{
  name: "list_bases",
  description: "List all accessible Airtable bases",
  inputSchema: {
    type: "object",
    properties: {},
    required: [],
  },
},

src/index.ts:80-84 (schema)
Input schema for list_bases tool: no parameters required.
```
inputSchema: {
  type: "object",
  properties: {},
  required: [],
},
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 2, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided; description implies read-only behavior but doesn't explicitly state it or mention any constraints like pagination. Adequate for a simple listing.

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

Conciseness5/5

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

Single concise sentence with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with zero parameters and no output schema, the description adequately conveys the core functionality. Could mention return format, but not critical.

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

Parameters4/5

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

No parameters, baseline 4. Description adds no parameter info but none needed.

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 'List all accessible Airtable bases' clearly specifies the action (list) and the resource (Airtable bases), distinguishing it from sibling tools like list_tables or list_records.

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?

No explicit guidance on when to use or when not. However, for a simple list tool with no parameters, the usage is straightforward and implicit.

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

Deploy Server