Skip to main content
Glama
onimsha

Airtable OAuth MCP Server

by onimsha

get_record

Retrieve a specific Airtable record by providing its base, table, and record IDs to access structured data through authenticated API calls.

Instructions

Get a specific record by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe Airtable base ID
table_idYesThe table ID or name
record_idYesThe record ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'get_record' that authenticates, calls AirtableClient.get_record, and formats the response.
    @self.mcp.tool(description="Get a specific record by ID")
    async def get_record(
        base_id: Annotated[str, Field(description="The Airtable base ID")],
        table_id: Annotated[str, Field(description="The table ID or name")],
        record_id: Annotated[str, Field(description="The record ID")],
    ) -> dict[str, Any]:
        """Get a specific record by ID."""
        client = await self._get_authenticated_client()
        record = await client.get_record(base_id, table_id, record_id)
    
        return {
            "id": record.id,
            "fields": record.fields,
            "createdTime": record.created_time,
        }
  • Pydantic schema defining input arguments for the get_record tool.
    class GetRecordArgs(BaseArgs):
        """Arguments for get_record tool."""
    
        base_id: str = Field(description="The Airtable base ID")
        table_id: str = Field(description="The table ID or name")
        record_id: str = Field(description="The record ID")
  • AirtableClient helper method that performs the actual HTTP GET request to retrieve a specific record from Airtable API.
    async def get_record(
        self,
        base_id: str,
        table_id: str,
        record_id: str,
    ) -> AirtableRecord:
        """Get a specific record by ID.
    
        Args:
            base_id: The Airtable base ID
            table_id: The table ID or name
            record_id: The record ID
    
        Returns:
            The requested record
        """
        logger.info(f"Getting record {record_id} from {base_id}/{table_id}")
    
        response = await self._make_request(
            "GET",
            f"/v0/{base_id}/{table_id}/{record_id}",
            response_model=AirtableRecord,
        )
    
        return response
  • FastMCP tool registration decorator for the get_record handler.
    @self.mcp.tool(description="Get a specific record by ID")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get') but doesn't describe whether this is a read-only operation, what happens if the ID is invalid (e.g., error handling), or any rate limits or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose without any wasted words. It's appropriately sized for a simple lookup tool, making it easy to parse and understand quickly.

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?

Given the tool's low complexity (a simple read operation), 100% schema coverage, and the presence of an output schema, the description is reasonably complete. It clearly states what the tool does, though it lacks behavioral details that would be helpful without annotations. The output schema likely covers return values, reducing the need for that in the description.

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 schema description coverage is 100%, with all three parameters clearly documented in the input schema. The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between base_id, table_id, and record_id. However, 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 'Get' and the resource 'a specific record by ID', making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list_records' or 'search_records', but the 'by ID' specification implies a direct lookup rather than filtering or listing.

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_records' or 'search_records'. It doesn't mention prerequisites, such as needing to know the exact record ID, or exclusions, such as not being suitable for bulk operations. Usage is implied but not explicitly stated.

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