Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_employees_create

Add a new employee to QuickBooks Online by providing a display name and optional contact, address, and employment details.

Instructions

Create a new Employee record in QuickBooks Online.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
DisplayNameYesDisplay name (required, must be unique)
GivenNameNoFirst name
FamilyNameNoLast name
MiddleNameNoMiddle name
PrimaryEmailAddrNoEmail, e.g. {"Address": "employee@example.com"}
PrimaryPhoneNoPhone, e.g. {"FreeFormNumber": "555-1234"}
PrimaryAddrNoHome address (Line1, City, CountrySubDivisionCode, PostalCode)
EmployeeNumberNoInternal employee number
BirthDateNoBirth date (YYYY-MM-DD)
HiredDateNoHire date (YYYY-MM-DD)
ReleasedDateNoTermination date (YYYY-MM-DD)
BillableTimeNoWhether the employee's time is billable to customers
ActiveNoWhether the employee is active
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It merely states the action without disclosing side effects (e.g., generated IDs), unique constraints (though schema mentions uniqueness), or any required authentication scope.

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 a single, direct sentence with no wasted words. It is efficient and to the point, though it could be expanded slightly for more context without losing conciseness.

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 (13 parameters, nested objects, no output schema, no annotations), the description is too brief. It lacks details on return values, validation behavior, or the effect of optional fields, making it incomplete for an agent.

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?

All 13 parameters have descriptions in the input schema (100% coverage). The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly specifies the action ('Create'), the resource ('Employee record'), and the context ('in QuickBooks Online'). It effectively distinguishes this tool from sibling tools like qbo_employees_get or qbo_employees_list.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when to create vs. update an employee, or any prerequisites like required permissions or data constraints.

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

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/wyre-technology/qbo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server