Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Execute QB command exec

execute_qb_command_exec
Read-onlyIdempotent

Builds a v2 qb_command_exec.execute request.

Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3150 missing_element, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3264 merchant_services_subscription_required

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "qb_command": "<qb_command>"
    },
    "name": "execute_qb_command_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentNo
qb_commandYes
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
bodyYesThe JSON body: the arguments you passed.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds real value beyond that: it says exactly what is returned (the v2 request plus the webhook payload shape and status codes) and enumerates ten error codes with names. It does not state authentication or rate-limit behavior, but the permission-related error codes partially compensate.

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 front-loaded with purpose and return behavior before the error catalog, so the most important content is read first. The ten-code error list is lengthy but organized and genuinely useful for handling failures. Minor bloat from enumerating every code rather than summarizing by category.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so detailed return-value explanation is not strictly required, yet the description goes further and characterizes the webhook/response_json channel. The notable gap is the `argument` array, which is the heart of a qb_command_exec call and is left entirely to the schema. Error coverage is thorough, so the definition is adequate but incomplete for a command-execution tool.

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?

With 50% schema description coverage, the description must compensate, and it does for two of four parameters: request_id is explained as the qbXML requestID echoed in response_xml, and include_qbxml is flagged as debug-only and not part of the v2 request. The nested `argument` array (arg_name/arg_value/list_id/txn_id) receives no explanation in the description, leaving the core of command execution undocumented.

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 states a specific verb and resource: it builds a v2 qb_command_exec.execute request and returns the request plus the webhook payload location. That framing distinguishes it from create_* siblings, which act directly, by making clear this is a request builder rather than an executor. It stops short of naming an explicit alternative for when a direct-execution tool exists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: build the request, send it, and handle the answer in the described webhook/response_json channel. There is no explicit when-to-use/when-not or comparison against sibling tools. The seven-value qb_command enum in the schema narrows scope, but the prose does not articulate selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources