Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create other name

create_other_name
Read-onlyIdempotent

Adds an other name. In QuickBooks, the “other names” list contains any names that don’t appear on customer, vendor, or employee lists.

The other_name_add wrapper from qbXML is also accepted. 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, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 3150 missing_element, 3175 in_use, 3176 locked, 3180 cannot_save, 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, 3263 read_only_access, 3264 merchant_services_subscription_required, 3270 missing_posting_account

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": {
      "name": "<name>"
    },
    "name": "create_other_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
faxNoFax number.
nameYesName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
emailNoE-mail address.
notesNoAdditional information.
phoneNoThe telephone number.
contactNoThe name of a contact person for a customer or vendor.
alt_phoneNoA telephone number given as an alternative to Phone.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
last_nameNoThe last name of a customer, vendor, employee, or person on the “other names” list.
first_nameNoThe first name of a customer, vendor, employee, or person on the “other names” list.
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`.
salutationNoA formal reference, such as Mr. or Dr., that precedes a name.
alt_contactNoThe name of an alternate contact person for a vendor, customer, or “other name” entry.
middle_nameNoThe middle name of a customer, vendor, employee, or person on the “other names” list.
company_nameNoThe name of the QuickBooks user’s business, as specified in QuickBooks. `company_name` and Address are used on invoices, checks, and other forms.
external_guidNoAllows for the attachment of a user defined GUID value.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
account_numberNoAccount numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs.
other_name_addressNoIf an address request fails, some combination of address fields might be too long.
include_ret_elementNo

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?

The description discloses the non-obvious two-phase design: the call returns the v2 request to send plus the webhook payload the answer arrives in, with `response_json` shape and status codes. This actually reconciles the readOnlyHint=true / idempotentHint=true annotations, since the tool compiles a request rather than mutating state directly. The enumerated error codes with numeric identifiers (3100 name_in_use, 3263 read_only_access, 3176 locked) add real operational context beyond annotations.

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

Conciseness3/5

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

The opening sentence is front-loaded and efficient, and the response/webhook explanation earns its place. However, the 17-error enumeration occupies a large share of the text and, since the description itself says "the call result explains each," it is largely redundant bulk.

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

Completeness4/5

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

For a 20-parameter nested create operation with an output schema, the description covers the things the schema cannot: the async request/webhook flow, the alias, and the failure modes. Address and field-level details are correctly left to a near-complete schema.

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 95%, so the parameters are already documented and the baseline applies. The description adds no per-parameter meaning beyond mentioning `other_name_add` as an accepted wrapper alias, which is a naming nuance rather than schema semantics.

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?

"Adds an other name" gives a specific verb and resource, and the follow-up sentence defines the QuickBooks "other names" list as names absent from customer, vendor, and employee lists, which is the differentiation an agent needs against the many create_* siblings. The sibling tools are never named, so the routing is inferential rather than explicit.

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?

The description establishes the domain and notes the qbXML alias `other_name_add` is accepted, which helps an agent map legacy terminology. It never states when to pick this over `update_other_name` or `create_customer`, nor does it give the prerequisite that a customer/vendor/employee name should not be reused.

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