Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_delete_record

Remove a specific record from a QuickBase table by providing the table ID and record ID. This tool simplifies data management within the QuickBase MCP Server.

Instructions

Delete a record from a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordIdYesRecord ID to delete
tableIdYesTable ID

Implementation Reference

  • Core implementation of the delete record logic using QuickBase REST API DELETE /records with where clause targeting the specific record ID (field 3).
    async deleteRecord(tableId: string, recordId: number): Promise<void> {
      await this.axios.delete('/records', {
        data: {
          from: tableId,
          where: `{3.EX.${recordId}}`
        }
      });
    }
  • src/index.ts:283-295 (registration)
    MCP server switch case handler that processes tool calls for quickbase_delete_record, validates arguments, calls the client method, and returns success response.
    case 'quickbase_delete_record':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.deleteRecord(args.tableId as string, args.recordId as number);
      return {
        content: [
          {
            type: 'text',
            text: `Record ${args.recordId} deleted successfully`,
          },
        ],
      };
  • Tool registration and input schema definition used by MCP server for listing and validating quickbase_delete_record tool parameters.
    {
      name: 'quickbase_delete_record',
      description: 'Delete a record from a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          recordId: { type: 'number', description: 'Record ID to delete' }
        },
        required: ['tableId', 'recordId']
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, the description fails to mention critical details such as whether deletion is permanent or reversible, what permissions are required, or if there are rate limits or side effects. This omission is significant for a tool that performs a destructive action.

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 that efficiently conveys the core action without unnecessary words. It is front-loaded with the key verb 'Delete' and avoids redundancy, making it easy for an AI agent to parse quickly. This brevity is effective for such a straightforward tool.

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 operation with no annotations and no output schema), the description is insufficient. It lacks details on behavioral aspects like permanence, permissions, or error handling, and does not explain what happens upon successful deletion (e.g., confirmation message or side effects). For a tool that modifies data, this level of incompleteness could lead to misuse by an AI agent.

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 documentation for both parameters ('recordId' and 'tableId'). The description does not add any semantic details beyond what the schema provides, such as explaining the relationship between these parameters or providing usage examples. However, since schema coverage is high, a baseline score of 3 is appropriate as the schema adequately handles parameter documentation.

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 target ('a record from a table'), which is specific and unambiguous. However, it does not differentiate this tool from sibling tools like 'quickbase_delete_field' or 'quickbase_delete_table', which also delete resources but different types. A perfect score would require explicit distinction from these alternatives.

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. For example, it does not mention when to choose 'quickbase_delete_record' over 'quickbase_delete_table' or other deletion tools, nor does it specify prerequisites or contexts for use. This lack of comparative or contextual advice limits its utility for an AI agent.

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