Skip to main content
Glama
onimsha

Airtable OAuth MCP Server

by onimsha

list_bases

Retrieve all accessible Airtable bases to view available workspaces and tables for data management and integration.

Instructions

List all accessible Airtable bases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler and registration for 'list_bases'. Decorated with @self.mcp.tool, it retrieves an authenticated AirtableClient and calls its list_bases() method, returning a list of base dictionaries.
    @self.mcp.tool(description="List all accessible Airtable bases")
    async def list_bases() -> list[dict[str, Any]]:
        """List all accessible Airtable bases."""
        client = await self._get_authenticated_client()
        response = await client.list_bases()
        return [
            {
                "id": base.id,
                "name": base.name,
                "permissionLevel": base.permission_level,
            }
            for base in response.bases
        ]
  • AirtableClient.list_bases() method, which makes the authenticated GET request to Airtable's /v0/meta/bases endpoint and parses the response using ListBasesResponse model.
    async def list_bases(self) -> ListBasesResponse:
        """List all accessible Airtable bases.
    
        Returns:
            Response containing list of bases
        """
        logger.info("Listing Airtable bases")
        return await self._make_request(
            "GET",
            "/v0/meta/bases",
            response_model=ListBasesResponse,
        )
  • Pydantic models AirtableBase and ListBasesResponse used for parsing the Airtable API response in list_bases.
    class AirtableBase(BaseModel):
        """Represents an Airtable base."""
    
        id: str
        name: str
        permission_level: str = Field(alias="permissionLevel")
    
    
    class ListBasesResponse(BaseModel):
        """Response from listing Airtable bases."""
    
        bases: list[AirtableBase]
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 what the tool does but doesn't describe any behavioral traits such as pagination, rate limits, sorting, or what 'accessible' means in terms of permissions. This leaves significant gaps for an agent to understand how to use it effectively.

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, clear sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and efficiently communicates the core functionality, making it easy for an agent to parse quickly.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, it lacks context about when to use it, behavioral details, and differentiation from siblings, which are important for a list operation in a server with multiple listing tools. The output schema helps, but the description should do more to guide usage.

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 the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here, but it doesn't compensate for any gaps since there are none. A baseline of 4 is given as it's complete for a no-parameter tool.

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 the resource 'all accessible Airtable bases', making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_tables' or 'list_records', which would require mentioning it's about bases rather than tables or records.

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 (e.g., authentication), context for when listing bases is appropriate, or how it differs from related tools like 'list_tables' or 'describe_table'.

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/onimsha/airtable-mcp-server-oauth'

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