Skip to main content
Glama
felores

Airtable MCP Server

by felores
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

list_tables

Retrieve all tables within an Airtable base by providing the base ID to manage and organize your data structure.

Instructions

List all tables in a base

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base

Implementation Reference

  • src/index.ts:409-418 (handler)
    Handler for the 'list_tables' tool. Extracts the base_id from the request arguments, fetches the list of tables from the Airtable API endpoint `/meta/bases/${base_id}/tables`, and returns the response data as formatted JSON text.
    case "list_tables": {
  const { base_id } = request.params.arguments as { base_id: string };
  const response = await this.axiosInstance.get(`/meta/bases/${base_id}/tables`);
  return {
    content: [{
      type: "text",
      text: JSON.stringify(response.data.tables, null, 2),
    }],
  };
}
  • src/index.ts:86-99 (registration)
    Registration of the 'list_tables' tool in the ListTools response, including its name, description, and input schema requiring a 'base_id'.
    {
  name: "list_tables",
  description: "List all tables in a base",
  inputSchema: {
    type: "object",
    properties: {
      base_id: {
        type: "string",
        description: "ID of the base",
      },
    },
    required: ["base_id"],
  },
},
  • src/index.ts:89-98 (schema)
    Input schema for the 'list_tables' tool, defining the required 'base_id' parameter as a string.
    inputSchema: {
  type: "object",
  properties: {
    base_id: {
      type: "string",
      description: "ID of the base",
    },
  },
  required: ["base_id"],
},

Tool Definition Quality

B3.1/5.0
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 the action but doesn't describe key behaviors: whether this is a read-only operation (implied but not explicit), if it requires specific permissions, what the output format looks like (e.g., list of table names or full metadata), or if there are pagination/rate limits. For a tool with zero annotation coverage, this leaves significant gaps.

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 with zero wasted words. It's front-loaded with the core action ('List all tables'), making it immediately scannable. Every word earns its place by conveying essential information without redundancy.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks context about behavioral traits, output format, or usage guidelines. For a simple list operation, this might suffice, but it doesn't provide enough information for confident tool selection in all scenarios.

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, with the single parameter 'base_id' clearly documented. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain what a 'base' is or where to find the ID). Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 tables in a base'), making the purpose immediately understandable. It distinguishes itself from siblings like list_bases (which lists bases) and list_records (which lists records within tables). However, it doesn't specify whether this includes hidden or system tables, which would make it a perfect 5.

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. It doesn't mention prerequisites (like needing a valid base_id), compare it to similar tools like list_bases, or indicate scenarios where other tools (like search_records for filtering) might be more appropriate. The agent must infer usage from the tool name alone.

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