Skip to main content
Glama
felores

Airtable MCP Server

by felores

update_table

Modify a table's schema in Airtable by updating its name and description to better organize your data structure.

Instructions

Update a table's schema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base
table_idYesID of the table to update
nameNoNew name for the table
descriptionNoNew description for the table

Implementation Reference

  • Handler for the 'update_table' tool. Extracts parameters from the request, makes a PATCH request to the Airtable API to update the table's name and/or description, and returns the response as text.
    case "update_table": {
      const { base_id, table_id, name, description } = request.params.arguments as {
        base_id: string;
        table_id: string;
        name?: string;
        description?: string;
      };
      
      const response = await this.axiosInstance.patch(`/meta/bases/${base_id}/tables/${table_id}`, {
        name,
        description,
      });
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify(response.data, null, 2),
        }],
      };
    }
  • src/index.ts:148-173 (registration)
    Registration of the 'update_table' tool in the listTools handler, including its name, description, and input schema definition.
    {
      name: "update_table",
      description: "Update a table's schema",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_id: {
            type: "string",
            description: "ID of the table to update",
          },
          name: {
            type: "string",
            description: "New name for the table",
          },
          description: {
            type: "string",
            description: "New description for the table",
          },
        },
        required: ["base_id", "table_id"],
      },
    },
  • Input schema definition for the 'update_table' tool, specifying required base_id and table_id, and optional name and description fields.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "ID of the base",
        },
        table_id: {
          type: "string",
          description: "ID of the table to update",
        },
        name: {
          type: "string",
          description: "New name for the table",
        },
        description: {
          type: "string",
          description: "New description for the table",
        },
      },
      required: ["base_id", "table_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 'Update a table's schema,' implying a mutation operation, but fails to describe critical behaviors: whether it requires specific permissions, if changes are reversible, what happens to existing data, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 is front-loaded with the core action and resource, making it easy to parse. Every word earns its place, achieving optimal conciseness without sacrificing clarity for the given content.

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 complexity of a mutation tool (updating a table schema) with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., side effects, permissions), usage context, and expected outcomes. While the schema covers parameters well, the overall context for safe and effective tool invocation is insufficient.

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 clear parameter documentation (e.g., 'ID of the base,' 'New name for the table'). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra credit is earned.

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 action ('Update') and the resource ('a table's schema'), making the purpose understandable. It distinguishes from siblings like 'update_record' or 'update_field' by specifying the table schema as the target. However, it doesn't explicitly mention what aspects of the schema can be updated (e.g., name, description), which prevents a perfect score.

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., needing base and table IDs), exclusions (e.g., not for updating table data), or comparisons to siblings like 'update_field' (for field-level changes) or 'create_table' (for new tables). This leaves the agent without context for tool selection.

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