Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_delete_table

Delete a specific table from QuickBase using its table ID. This MCP tool simplifies table management by enabling precise removal to maintain organized application structures.

Instructions

Delete a table from QuickBase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableIdYesQuickBase table ID to delete

Implementation Reference

  • Core implementation of the tool: sends DELETE request to QuickBase API endpoint /tables/{tableId} to delete the specified table.
    async deleteTable(tableId: string): Promise<void> {
      await this.axios.delete(`/tables/${tableId}`, {
        params: { appId: this.config.appId }
      });
    }
  • MCP CallToolRequest handler case that validates input arguments and delegates execution to QuickBaseClient.deleteTable method.
    case 'quickbase_delete_table':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.deleteTable(args.tableId as string);
      return {
        content: [
          {
            type: 'text',
            text: `Table ${args.tableId} deleted successfully`,
          },
        ],
      };
  • Tool registration object defining name, description, and JSON input schema for MCP tool listing.
    {
      name: 'quickbase_delete_table',
      description: 'Delete a table from QuickBase',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'QuickBase table ID to delete' }
        },
        required: ['tableId']
      }
    },
  • Zod schema for input validation matching the tool's tableId parameter.
    const TableIdSchema = z.object({
      tableId: z.string().describe('QuickBase table ID (e.g., "bu65pc8px")')
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('Delete') without behavioral details. It doesn't disclose if this is destructive (implied but not explicit), irreversible, requires admin permissions, has side effects (e.g., cascading deletions), or rate limits. 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 directly states the tool's action and target. It's appropriately sized for a simple operation and front-loaded with essential information.

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 (a destructive delete operation), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral risks, permissions, or what happens post-deletion (e.g., confirmation, error cases). For a mutation tool, this minimal description leaves critical gaps.

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 description coverage is 100%, with the single parameter 'tableId' documented as 'QuickBase table ID to delete'. The description adds no additional meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 ('Delete') and resource ('a table from QuickBase'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'quickbase_delete_field' or 'quickbase_delete_record', which would require specifying it's for tables specifically (though the name helps).

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 doesn't mention prerequisites (e.g., table must exist), exclusions (e.g., cannot delete if referenced), or compare to siblings like 'quickbase_delete_field' for field-level deletions. This leaves the agent without contextual usage cues.

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