Skip to main content
Glama
felores

Airtable MCP Server

by felores

update_field

Modify field properties in Airtable, including name, description, and configuration options, to adapt database structures as project requirements evolve.

Instructions

Update a field in a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesID of the base
table_idYesID of the table
field_idYesID of the field to update
updatesYes

Implementation Reference

  • The handler function for the 'update_field' tool. It extracts parameters from the request, makes a PATCH request to the Airtable API to update the field, and returns the response as text content.
    case "update_field": {
      const { base_id, table_id, field_id, updates } = request.params.arguments as {
        base_id: string;
        table_id: string;
        field_id: string;
        updates: Partial<FieldOption>;
      };
      
      const response = await this.axiosInstance.patch(
        `/meta/bases/${base_id}/tables/${table_id}/fields/${field_id}`,
        updates
      );
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify(response.data, null, 2),
        }],
      };
    }
  • The tool registration and input schema definition for 'update_field' returned by the list_tools handler.
    {
      name: "update_field",
      description: "Update a field in a table",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "ID of the base",
          },
          table_id: {
            type: "string",
            description: "ID of the table",
          },
          field_id: {
            type: "string",
            description: "ID of the field to update",
          },
          updates: {
            type: "object",
            properties: {
              name: {
                type: "string",
                description: "New name for the field",
              },
              description: {
                type: "string",
                description: "New description for the field",
              },
              options: {
                type: "object",
                description: "New field-specific options",
              },
            },
          },
        },
        required: ["base_id", "table_id", "field_id", "updates"],
      },
    },
  • Type definition for FieldOption used in the updates parameter (as Partial<FieldOption>) for the update_field tool.
    export interface FieldOption {
      name: string;
      type: FieldType;
      description?: string;
      options?: Record<string, any>;
    }
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 this is an update operation, implying mutation, but doesn't mention permissions required, whether changes are reversible, rate limits, or what happens to existing field data. 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 waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 mutation tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'updates' contains, how options are structured, or what the tool returns. Given the complexity and lack of structured data, more context is needed to guide the agent effectively.

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 doesn't add any parameter-specific information beyond what's in the input schema, which has 75% coverage. It doesn't explain the structure of 'updates' or clarify the purpose of IDs like 'base_id' and 'table_id'. Since schema coverage is moderate, the baseline score of 3 is appropriate, but the description doesn't compensate for the 25% gap.

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 ('Update') and resource ('a field in a table'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'update_table' or 'update_record', which also perform updates on related resources in the same system.

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?

No guidance is provided on when to use this tool versus alternatives like 'update_table' or 'update_record'. The description lacks context about prerequisites (e.g., needing existing base/table/field IDs) or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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