Skip to main content
Glama
felores

Airtable MCP Server

by felores

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
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • 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: [],
      },
    },
  • Input schema for list_bases tool: no parameters required.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it lists 'accessible' bases, implying some permission-based filtering, but doesn't specify what 'accessible' means, whether it requires authentication, or details about the return format (e.g., pagination, fields included). This leaves significant gaps for a tool with zero annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool with no parameters.

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 tool's simplicity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'accessible' entails, the format of returned data, or any behavioral aspects like error handling, making it inadequate for full agent understanding despite the low complexity.

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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description appropriately doesn't discuss parameters, as there are none to explain, which aligns well with the schema.

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 verb ('List') and resource ('all accessible Airtable bases'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'list_tables' or 'list_records', which would require mentioning it returns bases rather than tables or records, so it lacks full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_tables' or 'list_records'. It doesn't mention prerequisites, such as needing authentication or specific permissions to access bases, or any context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/felores/airtable-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server