Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_update_record

Modifies an existing record in QuickBase by specifying the table ID, record ID, and updated field values for precise data management.

Instructions

Update an existing record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesField values to update as fieldId: {value: actualValue} pairs
recordIdYesRecord ID to update
tableIdYesTable ID

Implementation Reference

  • Core handler function that executes the QuickBase API call to update a specific record using the provided table ID, record ID, and field updates.
    async updateRecord(tableId: string, recordId: number, updates: Record<string, any>): Promise<void> {
      await this.axios.post('/records', {
        to: tableId,
        data: [{
          '3': { value: recordId }, // Record ID field
          ...updates
        }]
      });
    }
  • MCP server dispatch handler case that validates arguments and delegates to QuickBaseClient.updateRecord method.
    case 'quickbase_update_record':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.updateRecord(
        args.tableId as string, 
        args.recordId as number, 
        args.fields as Record<string, any>
      );
      return {
        content: [
          {
            type: 'text',
            text: `Record ${args.recordId} updated successfully`,
          },
        ],
      };
  • Tool registration definition including name, description, and input schema for the MCP tool list.
    {
      name: 'quickbase_update_record',
      description: 'Update an existing record',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          recordId: { type: 'number', description: 'Record ID to update' },
          fields: { 
            type: 'object', 
            description: 'Field values to update as fieldId: {value: actualValue} pairs',
            additionalProperties: true
          }
        },
        required: ['tableId', 'recordId', 'fields']
      }
    },
  • Zod schema definition for input validation of the update_record tool parameters.
    const UpdateRecordSchema = z.object({
      tableId: z.string().describe('Table ID'),
      recordId: z.number().describe('Record ID to update'),
      fields: z.record(z.any()).describe('Field values to update as fieldId: value pairs')
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, it doesn't specify permissions required, whether the update is atomic or partial, what happens on failure, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core action and resource, making it efficient for quick scanning by an AI agent.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address behavioral aspects like error handling, response format, or side effects, nor does it help differentiate from sibling tools. Given the complexity of updating records in a database context, more completeness is needed.

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 schema description coverage is 100%, so the input schema already documents all three parameters thoroughly. The description adds no additional meaning beyond what's in the schema, such as explaining relationships between parameters or providing examples. This meets the baseline for high schema coverage.

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 ('Update') and resource ('an existing record'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'quickbase_update_field', which also performs updates but on a different resource type.

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 like 'quickbase_update_field' or 'quickbase_bulk_create_records'. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent with minimal contextual direction.

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