Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_delete_field

Remove a specific field from a QuickBase table by specifying the table ID and field ID using this tool. Simplifies field management and maintains table structure.

Instructions

Delete a field from a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldIdYesField ID to delete
tableIdYesTable ID

Implementation Reference

  • Core implementation of deleting a QuickBase field via API DELETE request to /fields/{fieldId} with tableId parameter.
    async deleteField(tableId: string, fieldId: number): Promise<void> {
      await this.axios.delete(`/fields/${fieldId}`, {
        params: { tableId }
      });
    }
  • MCP server handler for quickbase_delete_field tool call, validates args and delegates to QuickBaseClient.deleteField.
    case 'quickbase_delete_field':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.deleteField(args.tableId as string, args.fieldId as number);
      return {
        content: [
          {
            type: 'text',
            text: `Field ${args.fieldId} deleted successfully`,
          },
        ],
      };
  • Tool registration entry in quickbaseTools array, including name, description, and input schema for validation.
    {
      name: 'quickbase_delete_field',
      description: 'Delete a field from a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          fieldId: { type: 'number', description: 'Field ID to delete' }
        },
        required: ['tableId', 'fieldId']
      }
    },
  • Input schema definition for quickbase_delete_field tool parameters: tableId (string) and fieldId (number), both required.
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          fieldId: { type: 'number', description: 'Field ID to delete' }
        },
        required: ['tableId', 'fieldId']
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action is a deletion, implying a destructive mutation, but fails to mention critical details such as permissions required, whether the deletion is permanent or reversible, impact on related data, or error handling, which are essential for a destructive operation.

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, direct sentence with no unnecessary words, making it highly concise and front-loaded. It efficiently communicates the core action without redundancy, earning a top score for brevity and clarity.

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's complexity as a destructive mutation with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects (e.g., safety, side effects), usage context, or expected outcomes, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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 definitions for 'fieldId' and 'tableId'. The description does not add any semantic details beyond the schema, such as format examples or constraints, but since schema coverage is high, the baseline score of 3 is appropriate as the schema adequately documents the parameters.

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 ('Delete') and the resource ('a field from a table'), making the purpose immediately understandable. However, it does not differentiate this tool from sibling tools like 'quickbase_delete_record' or 'quickbase_delete_table', which also perform deletion operations on different resources, so it lacks sibling distinction.

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 does not mention prerequisites (e.g., field must exist), exclusions (e.g., cannot delete certain field types), or refer to related tools like 'quickbase_update_field' or 'quickbase_create_field' for context, leaving usage unclear.

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

Related 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/LawrenceCirillo/QuickBase-MCP-Server'

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