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"],
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the action. It does not disclose whether updates are idempotent, require special permissions, or affect existing data. The optional parameters suggest partial updates, but this is not explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it could be slightly expanded to include usage context without losing conciseness.

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 tool has 4 parameters, no output schema, and no annotations, the description is insufficient for an agent to fully understand when and how to use it. Sibling tools exist but no differentiation is provided.

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?

Schema coverage is 100%, so the parameter meanings are clear from the schema. The description adds no extra context beyond what is in the schema, such as constraints on name or description values.

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 'Update a table's schema' clearly states the action and resource, and distinguishes from sibling tools like update_field and update_view. However, 'schema' could be misinterpreted as structural schema changes, while the parameters only allow updating name and description.

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 update_field or update_view. No context about prerequisites or typical use cases is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.