Skip to main content
Glama
felores

Airtable MCP Server

by felores

get_record

Retrieve a specific record from an Airtable base using its unique ID, table name, and base ID for targeted data access.

Instructions

Get a single record by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base
table_nameYesName of the table
record_idYesID of the record to retrieve

Implementation Reference

  • src/index.ts:371-392 (registration)
    Registration of the 'get_record' tool in the ListTools response. Defines the tool name, description, and input schema specifying base_id, table_name, and record_id as required string parameters.
    {
      name: "get_record",
      description: "Get a single record by its ID",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_name: {
            type: "string",
            description: "Name of the table",
          },
          record_id: {
            type: "string",
            description: "ID of the record to retrieve",
          },
        },
        required: ["base_id", "table_name", "record_id"],
      },
    },
  • The handler function for the 'get_record' tool. Extracts base_id, table_name, and record_id from arguments, makes a GET request to the Airtable API endpoint for the specific record, and returns the response data as formatted JSON text.
    case "get_record": {
      const { base_id, table_name, record_id } = request.params.arguments as {
        base_id: string;
        table_name: string;
        record_id: string;
      };
      const response = await this.axiosInstance.get(
        `/${base_id}/${table_name}/${record_id}`
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(response.data, null, 2),
        }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention permission requirements, error handling (e.g., what happens if ID doesn't exist), rate limits, or response format. This leaves significant gaps for a tool that interacts with data.

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 with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information about what the tool does.

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?

For a data retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'record' contains, what format the response takes, or any behavioral aspects like error conditions. Given the complexity of interacting with a database-like system and the lack of structured metadata, more context is needed.

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 description mentions retrieving by 'ID' which maps to the 'record_id' parameter, but doesn't explain the purpose of 'base_id' and 'table_name' parameters or their relationship. With 100% schema description coverage, the schema documents all parameters adequately, so the description adds minimal value beyond what's already in the structured data.

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 tool's purpose with a specific verb ('Get') and resource ('a single record'), and specifies the key identifier ('by its ID'). However, it doesn't explicitly differentiate from sibling tools like 'list_records' or 'search_records' which also retrieve records but with different approaches.

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' (for multiple records) or 'search_records' (for query-based retrieval). It mentions the ID requirement but doesn't explain when direct ID lookup is preferred over other methods.

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