QuickBooks Online MCP Server

update_employee

Update an existing employee in QuickBooks Online to keep employee details accurate for payroll and reporting.

Instructions

Update an employee in QuickBooks Online.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses essentially nothing beyond mutation intent. It does not say whether this is a full replacement or partial patch, which fields are updatable, whether omitted fields are cleared, what permissions or identifiers are required, or whether changes are reversible.

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

Conciseness2/5

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

It is a single short sentence, so there is no bloat, but it is under-specified rather than concise—it largely restates the tool name and adds only the product name. No sentence adds actionable information.

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

Completeness1/5

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

A mutation tool with no annotations, no output schema, and a completely undocumented nested object payload needs far more than one line. An agent cannot construct a valid call from this definition alone; at minimum the updatable fields, required identifiers, and update semantics are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is a nested object whose inner "employee" property has an empty schema with additionalProperties allowed. The description adds nothing about the shape, required fields, or expected format (e.g., Id, SyncToken, sparse-update semantics), leaving the caller to guess the entire payload.

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?

States a specific verb and resource ("Update an employee") plus the system (QuickBooks Online), so an agent knows it mutates an existing employee record rather than creating, deleting, or reading one. It offers no explicit differentiation from siblings such as update_customer, update_vendor, or update-item, but the resource name is unambiguous.

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: nothing says to prefer this over delete_employee, get_employee, or search_employees, nor any prerequisite such as needing an existing employee ID. The only usable cue is the verb "update," which is already in the name.

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

Deploy Server