Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_create_record

Add a new record to a specified table in QuickBase using defined field values. Simplify data entry and organization directly via the QuickBase MCP Server.

Instructions

Create a new record in a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesField values as fieldId: {value: actualValue} pairs
tableIdYesTable ID to create record in

Implementation Reference

  • MCP tool handler for 'quickbase_create_record' that extracts arguments, calls QuickBaseClient.createRecord, and returns a success message with the new record ID.
    case 'quickbase_create_record':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      const newRecordId = await this.qbClient.createRecord(args.tableId as string, {
        fields: args.fields as Record<string, any>
      });
      return {
        content: [
          {
            type: 'text',
            text: `Record created with ID: ${newRecordId}`,
          },
        ],
      };
  • Zod schema definition for validating input to quickbase_create_record tool.
    const CreateRecordSchema = z.object({
      tableId: z.string().describe('Table ID to create record in'),
      fields: z.record(z.any()).describe('Field values as fieldId: value pairs')
    });
  • Tool registration in quickbaseTools array, including name, description, and inputSchema for ListTools endpoint.
    {
      name: 'quickbase_create_record',
      description: 'Create a new record in a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID to create record in' },
          fields: { 
            type: 'object', 
            description: 'Field values as fieldId: {value: actualValue} pairs',
            additionalProperties: true
          }
        },
        required: ['tableId', 'fields']
      }
    },
  • Core implementation of record creation via QuickBase API POST /records, extracting new record ID from field 3.
    async createRecord(tableId: string, record: QuickBaseRecord): Promise<number> {
      const response = await this.axios.post('/records', {
        to: tableId,
        data: [{
          ...record.fields
        }]
      });
      return response.data.data[0]['3'].value; // Record ID is always field 3
    }
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. It states the tool creates a record, implying a write operation, but lacks details on permissions, side effects, error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage, as it doesn't address critical behavioral traits like what happens on failure or if the table doesn't exist.

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—'Create a new record in a table'—front-loading the core action and resource. It's appropriately sized for the tool's purpose, making it easy to parse without unnecessary elaboration.

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 write operation with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or how it interacts with sibling tools. For a mutation tool in a rich ecosystem like Quickbase, more context is needed to ensure proper agent usage.

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 (tableId and fields). The description adds no additional meaning beyond what the schema provides, such as examples or constraints on field values. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new record in a table' clearly states the action (create) and resource (record in a table), but it's vague about scope and doesn't differentiate from siblings like 'quickbase_bulk_create_records' or 'quickbase_create_table'. It specifies the basic operation but lacks precision about what distinguishes this specific tool.

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?

No guidance is provided on when to use this tool versus alternatives such as 'quickbase_bulk_create_records' for multiple records or 'quickbase_create_table' for creating tables. The description implies usage for single-record creation but offers no explicit context, prerequisites, or exclusions, leaving the agent to infer based on tool names alone.

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