Skip to main content
Glama

delete_field

Destructive

Delete a field from an Airtable table using its ID and expected name. Deletion is irreversible and blocked if dependencies exist unless force is enabled.

Instructions

Delete a field from an Airtable table. Requires fieldId AND expectedName as a safety guard — deletion is refused if the name does not match. ⚠️ Irreversible: deleted field data is permanently lost and cannot be recovered. Always checks downstream dependencies first (formula fields, lookups, rollups referencing this field); returns dependency info without deleting unless force=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
fieldIdYesThe field/column ID to delete (e.g. "fldXXX")
expectedNameYesThe expected name of the field. Must match exactly or deletion is refused.
forceNoWhen true, delete even if the field has downstream dependencies (other fields referencing it). Default: false.
debugNoWhen true, include raw Airtable response in output for diagnostics
Behavior5/5

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

Adds irreversibility warning, dependency check behavior, and force flag effect, all beyond annotations' destructiveHint.

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?

Three concise sentences, front-loaded with action and guard, no unnecessary 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?

Fully explains all key aspects for a 5-param tool with no output schema: safety, irreversibility, dependencies, debug option.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning: expectedName as safety guard, force as dependency override, debug for diagnostics, beyond schema descriptions.

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 'delete' and resource 'field from an Airtable table'. Distinct from siblings like 'delete_fields' and 'create_field'.

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?

Explains safety guard requiring expectedName and force parameter for dependencies, but doesn't explicitly contrast with delete_fields or state when not to use.

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