Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_search_records

Search for specific text within records in a QuickBase table. Input the table ID, search term, and optional field IDs to locate relevant data efficiently.

Instructions

Search for records containing specific text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldIdsNoField IDs to search in
searchTermYesText to search for
tableIdYesTable ID to search

Implementation Reference

  • Core handler function that implements record search by building a QuickBase 'where' clause with 'CT' (contains text) operator on specified fieldIds or defaults to fields 6 and 7, then delegates to getRecords method.
    async searchRecords(tableId: string, searchTerm: string, fieldIds?: number[]): Promise<any[]> {
      // This is a simple implementation - you might want to enhance based on your search needs
      const whereClause = fieldIds 
        ? fieldIds.map(fieldId => `{${fieldId}.CT.'${searchTerm}'}`).join('OR')
        : `{6.CT.'${searchTerm}'}OR{7.CT.'${searchTerm}'}`; // Common text fields
    
      return this.getRecords(tableId, { where: whereClause });
    }
  • src/index.ts:314-330 (registration)
    MCP server registration and dispatch handler for 'quickbase_search_records' tool, parses arguments and calls QuickBaseClient.searchRecords, formats response as JSON text.
    case 'quickbase_search_records':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      const searchResults = await this.qbClient.searchRecords(
        args.tableId as string, 
        args.searchTerm as string, 
        args.fieldIds as number[]
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(searchResults, null, 2),
          },
        ],
      };
  • Zod schema for validating input parameters of quickbase_search_records tool.
    const SearchRecordsSchema = z.object({
      tableId: z.string().describe('Table ID to search'),
      searchTerm: z.string().describe('Text to search for'),
      fieldIds: z.array(z.number()).optional().describe('Field IDs to search in')
    });
  • Tool definition including inputSchema used for MCP tool listing and validation.
      name: 'quickbase_search_records',
      description: 'Search for records containing specific text',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID to search' },
          searchTerm: { type: 'string', description: 'Text to search for' },
          fieldIds: { type: 'array', items: { type: 'number' }, description: 'Field IDs to search in' }
        },
        required: ['tableId', 'searchTerm']
      }
    },
  • src/index.ts:50-52 (registration)
    MCP server registers all tools including quickbase_search_records via quickbaseTools export from tools/index.ts.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: quickbaseTools,
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions searching but doesn't describe what 'search' entails operationally - whether it's case-sensitive, supports wildcards, returns partial matches, has pagination, or what the output format looks like. This leaves significant gaps for a tool with 3 parameters.

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 6 words, with zero wasted language. It's front-loaded with the core action and gets straight to the point 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?

For a search tool with 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain the search behavior, result format, limitations, or how it differs from other data retrieval tools in the sibling set. The agent would struggle to use this effectively without additional context.

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%, so the schema already documents all parameters adequately. The description adds no additional semantic context about parameters beyond the basic search concept. It doesn't explain relationships between parameters or provide usage examples.

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 'Search for records containing specific text' states the basic action (search) and resource (records), but is vague about scope and differentiation. It doesn't specify whether this is a full-text search, field-specific search, or how it differs from sibling tools like 'quickbase_query_records' or 'quickbase_run_report'.

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 about when to use this tool versus alternatives. With multiple sibling tools for data retrieval (query_records, run_report, get_record), the description offers no context about appropriate use cases, prerequisites, or exclusions.

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