Skip to main content
Glama

update_formula_field

Idempotent

Update the formula expression of an existing formula field in an Airtable base. Specify the base, field, and new formula text to modify field behavior.

Instructions

Update the formula text of an existing formula field. Shorthand for update_field_config with type "formula".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
fieldIdYesThe field/column ID (e.g. "fldXXX")
formulaTextYesThe new formula text
debugNoWhen true, include raw Airtable response in output for diagnostics

Implementation Reference

  • The tool handler function that executes update_formula_field logic. It delegates to update_field_config with fieldType='formula' and the provided formulaText as typeOptions.
    async update_formula_field({ appId, fieldId, formulaText, debug }) {
      return handlers.update_field_config({
        appId, fieldId,
        fieldType: 'formula',
        typeOptions: { formulaText },
        debug,
      });
    },
  • Input schema (JSON Schema) for the update_formula_field tool, defining required parameters: appId, fieldId, formulaText, and optional debug.
    {
      name: 'update_formula_field',
      description: 'Update the formula text of an existing formula field. Shorthand for update_field_config with type "formula".',
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          appId: { type: 'string', description: 'The Airtable base/application ID' },
          fieldId: { type: 'string', description: 'The field/column ID (e.g. "fldXXX")' },
          formulaText: { type: 'string', description: 'The new formula text' },
          debug: debugProp,
        },
        required: ['appId', 'fieldId', 'formulaText'],
      },
    },
  • Tool registration in the tool-config.js TOOL_CATEGORIES mapping, categorizing it as 'field-write'.
    update_formula_field:   'field-write',
  • Duplicate registration in the extension's tool-profile.ts TOOL_CATEGORIES mapping, also categorized as 'field-write'.
    update_formula_field:      'field-write',
  • The underlying AirtableClient.updateFieldConfig method that actually calls the Airtable internal API (POST /v0.3/column/{id}/updateConfig) to update the field configuration. This is what update_formula_field ultimately delegates to via update_field_config.
    async updateFieldConfig(appId, columnId, config) {
      assertAirtableId(appId, 'appId');
      assertAirtableId(columnId, 'columnId');
      await this.resolveField(appId, columnId);
    
      const url = `https://airtable.com/v0.3/column/${columnId}/updateConfig`;
    
      const normalized = normalizeFieldType(config.type, config.typeOptions);
    
      // Flat payload — matches real Airtable requests
      const payload = {
        type: normalized.type,
        typeOptions: normalized.typeOptions,
      };
    
      const res = await this.auth.postForm(url, this._mutationParams(payload, appId), appId);
    
      if (!res.ok) {
        const errBody = await res.text().catch(() => '');
        throw new Error(`updateFieldConfig failed (${res.status}): ${errBody}`);
      }
    
      this.cache.invalidate(appId);
      return res.json();
    }
Behavior3/5

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

Annotations already declare idempotentHint=true and non-destructive; description adds minimal extra beyond being a shorthand. No added behavioral context (e.g., triggers, permissions).

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?

Two efficient sentences with no filler. Purpose and shorthand relationship clearly stated in minimal words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool, good annotations, and complete schema, the description provides sufficient context for correct selection and invocation.

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?

Input schema has 100% coverage with clear descriptions for all 4 parameters. Description does not add further meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb and resource: 'Update the formula text of an existing formula field.' Differentiates from siblings by noting it's a shorthand for update_field_config with type 'formula'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states it's a shorthand for update_field_config with type 'formula', implying use when only updating formula text; does not explicitly list when not to use or alternatives.

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/Automations-Project/VSCode-Airtable-Formula'

If you have feedback or need assistance with the MCP directory API, please join our Discord server