Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create employee

create_employee
Read-onlyIdempotent

Adds an employee with personal data about the employee as well as certain payroll-related data.

The employee_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, 3000 invalid_object_id, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 3120 object_not_found, 3140 invalid_reference, 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_employee"
  }
}

Input Schema

NameRequiredDescriptionDefault
faxNoFax number.
ssnNoSocial security number. When you add an SSN value to an employee record, it doesn’t have to include dashes; for example, either 123-45-6789 or 123456789 would be valid.
nameNoA concatenation of `first_name`, `middle_name`, and `last_name`.
emailNoE-mail address.
notesNoAdditional information.
pagerNoThe pager number.
phoneNoThe telephone number.
exemptNoExempt or Non-exempt status of the employee.
genderNoThe gender of this employee.
mobileNoMobile telephone number.
suffixNo
on_fileNoIs the employee’s I-9 on file?
disabledNoIs employee disabled?
print_asNoBy default within QuickBooks, the `print_as` element is the same as the Name element.
alt_phoneNoA telephone number given as an alternative to Phone.
ethnicityNoEthnicity of employee from AmericianIndian, Asian, Black, Hawaiian, Hispanic, White, TwoOrMoreRaces
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
job_titleNoThe job title of a customer, vendor, employee, or person on the “other names” list.
last_nameNoThe last name of a customer, vendor, employee, or person on the “other names” list.
pager_pinNoA personal identification number for this employee’s pager.
birth_dateNoDate of birth.
departmentNoThe name of the department in the employment job details section.
first_nameNoThe first name of a customer, vendor, employee, or person on the “other names” list.
hired_dateNoAn employee’s date of hire.
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.
us_citizenNoIs employee a US citizen?
us_veteranNoIs employee a US veteran?
descriptionNoThe description details in the employment job details section.
middle_nameNoThe middle name of a customer, vendor, employee, or person on the “other names” list.
key_employeeNoIs employee a key or critical employee.
target_bonusNoThe target bonus amount in the employment job details section.
employee_typeNo`employee_type` can affect payroll taxes for an employee. A statutory employee is a person who is defined as an employee by statute.
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.
released_dateNoThe date on which this person’s employment with the company ended.
account_numberNoAccount numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs.
supervisor_refNoThe name of a customer, vendor, employee, or person on the “other names” list in the employment job details section.
disability_descNoDescription of employee’s disablitily.
military_statusNoMilitary status if the employee is a US veteran.
additional_notesNo
billing_rate_refNoBilling rates are used to override the service item rate in a time transaction (TimeTrackingAdd) based on the employee or vendor performing the work.
employee_addressNoIf an address request fails, some combination of address fields might be too long.
part_or_full_timeNoFull or Part time status of the employee.
emergency_contactsNoEmergency Contact information for the employee.
original_hire_dateNoOriginal hire date the employee was hired.
include_ret_elementNo
adjusted_service_dateNoAdjusted service date for the employee.
employee_payroll_infoNoPay information for this employee.
work_auth_expire_dateNoDate the employee’s work authorization expires.
additional_contact_refNo

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

C2.7/5.0
Behavior1/5

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

The description says the tool "Adds an employee", a write operation, while the annotations declare readOnlyHint=true and destructiveHint=false. That is a direct contradiction of the declared safety profile. The useful behavioral content it does carry (error codes, webhook delivery model) cannot offset the misleading mutability signal.

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 first sentence and the return-value sentence are front-loaded and earn their place, but the bulk of the description is a 20-item error dump that reads as raw enum spillover rather than curated guidance. The parenthetical about response_json is awkwardly embedded and interrupts flow.

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?

For a 51-parameter creation tool with nested payroll aggregates, the description surfaces the async webhook/response model and error taxonomy, which is genuinely useful, and an output schema exists. However, it says nothing about minimum viable input (zero required parameters) or payroll subscription prerequisites, even though it lists 3262 payroll_subscription_required as an error.

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 92%, so nearly every one of the 51 parameters is already documented in the schema; the description adds no field-level meaning of its own. Its only parameter-adjacent contribution is noting that `employee_add` qbXML is accepted and that `request_id` is optional, which is marginal beyond the schema.

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 opening sentence states a specific verb and resource ("Adds an employee") plus the two data domains covered (personal and payroll-related). It is clearly distinguishable from update_employee by verb alone, though it never names that sibling explicitly.

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?

There is no when-to-use guidance, no exclusions, and no pointer to update_employee for the modify case. The only routing hint is that the `employee_add` qbXML wrapper is also accepted, which is input-form guidance rather than tool-selection guidance.

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