Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_run_report

Execute a specific report in QuickBase by providing the Report ID and Table ID, enabling efficient data management and analysis within the MCP server.

Instructions

Run a specific report

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportIdYesReport ID
tableIdYesTable ID

Implementation Reference

  • Core handler function in QuickBaseClient that executes the QuickBase API call to run the specified report and returns the report data.
    async runReport(reportId: string, tableId: string): Promise<any[]> {
      const response = await this.axios.post('/records/query', {
        from: tableId,
        options: {
          reportId
        }
      });
      return response.data.data;
    }
  • MCP server handler that dispatches the tool call to the QuickBaseClient.runReport method and formats the response.
    case 'quickbase_run_report':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              await this.qbClient.runReport(args.reportId as string, args.tableId as string), 
              null, 
              2
            ),
          },
        ],
      };
  • Tool schema definition including input schema for parameters reportId and tableId, used for registration and validation.
      name: 'quickbase_run_report',
      description: 'Run a specific report',
      inputSchema: {
        type: 'object',
        properties: {
          reportId: { type: 'string', description: 'Report ID' },
          tableId: { type: 'string', description: 'Table ID' }
        },
        required: ['reportId', 'tableId']
      }
    },
  • src/index.ts:51-52 (registration)
    Registration of all QuickBase tools including quickbase_run_report via the listTools handler.
    return {
      tools: quickbaseTools,
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. 'Run a specific report' implies a read-only operation, but it doesn't specify whether this is safe, if it requires permissions, what the output format is, or any rate limits. For a tool with no annotation coverage, this is a significant gap in describing behavior beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a single sentence, 'Run a specific report', which is front-loaded and wastes no words. However, it's overly brief to the point of under-specification, lacking necessary details for clarity. It earns a 4 for efficiency but loses points for not providing enough substance.

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 complexity of running a report (likely involving data retrieval and formatting), no annotations, no output schema, and a vague description, this is incomplete. The description doesn't cover what the tool returns, any behavioral traits, or how it differs from siblings. For a tool in a rich server context with many alternatives, more detail is needed to be adequately helpful.

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 both parameters (reportId and tableId) documented in the schema. The description doesn't add any meaning beyond what the schema provides—it doesn't explain why both IDs are needed or how they relate. Since the schema does the heavy lifting, 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.

Purpose2/5

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

The description 'Run a specific report' is a tautology that essentially restates the tool name 'quickbase_run_report'. It specifies the verb 'run' and resource 'report', but lacks any distinguishing details about what running a report entails (e.g., executing a predefined query, returning formatted data). Compared to siblings like 'quickbase_query_records' or 'quickbase_get_reports', it doesn't clarify how this differs.

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. Sibling tools include 'quickbase_query_records' and 'quickbase_search_records', which might serve similar data retrieval purposes, but the description doesn't explain when a report is preferred over a direct query or search. There's no mention of prerequisites, context, 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