QuickBooks Online MCP Server

create_term

Creates a new payment term in QuickBooks Online, such as Net 30 or Due on Receipt, so invoices and billing workflows can use consistent due-date rules.

Instructions

Create a new payment term in QuickBooks Online (e.g., Net 30, Due on Receipt).

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": "create_term"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.9/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 burden of behavioral disclosure, yet it only implies mutation via the verb 'Create'. It says nothing about required permissions, duplicate-name handling, which fields are mutually exclusive per term type (STANDARD vs DATE_DRIVEN), or what the call returns (a created term with an ID?). For an unannotated write tool this is a substantial gap.

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?

A single front-loaded sentence with zero filler, and the parenthetical examples add practical value rather than noise. It is efficiently written, though efficiency here partly reflects under-specification rather than disciplined trimming.

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?

The tool is a nested-object mutation with no annotations and no output schema, and the description covers only the bare purpose. It omits guidance on filling the nested 'params' object and on the conditional field rules, so an agent has enough to identify the tool but not enough to call it correctly on the first try.

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

Parameters2/5

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

The description mentions no parameters at all — not the required 'name', nor the conditional relationship between 'type' and fields like 'due_days' or 'day_of_month_due'. Reporting 0% schema description coverage at the top level (the nested 'params' wrapper is undocumented), the description fails to compensate for the gap, leaving callers to reverse-engineer the payload shape.

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?

Uses a specific verb and resource ('Create a new payment term in QuickBooks Online') and anchors it with concrete examples (Net 30, Due on Receipt) that make the domain unambiguous. It does not explicitly distinguish itself from update_term, get_term, or search_terms, but the create verb plus the tool name leave no real ambiguity.

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 contains no when-to-use guidance: nothing about preconditions (e.g., whether a term must be unique, whether search_terms should be checked first), no mention of when not to call it, and no reference to the sibling update_term/search_terms alternatives. An agent must infer all routing decisions from the tool name alone.

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

Deploy Server