Skip to main content
Glama
Lunar-Software-Solution

QuickBooks Online MCP Server

delete_item

Deactivate an item in QuickBooks Online by specifying its ID or entity.

Instructions

Delete (make inactive) an item in QuickBooks Online.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes
companyNoTarget QuickBooks company as its realm ID (e.g. 1234567890123456). Optional — if omitted, the connection's default company is used.
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It notes 'make inactive' implying a non-destructive deletion, but lacks details on reversibility, permissions, side effects, or return values. For a deletion tool, more transparency is needed.

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, concise sentence that imparts the core purpose without excess. However, it could be slightly more structured to include usage hints.

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 (nested object, no output schema) and the presence of many sibling delete tools, the description is too minimal. It does not explain how to identify the item (idOrEntity format), success/failure responses, or any constraints.

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?

Schema description coverage is 50% (only 'company' is described). The description adds no explanation for the 'params' object or 'idOrEntity', leaving key parameters undocumented. It does not compensate for the missing schema coverage.

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 states the action (delete/make inactive) and the resource (item in QuickBooks Online). It distinguishes from sibling tools by specifying 'item' as the target, which is unique among many delete tools.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., other delete tools) or when not to use it. The description only states what it does, not the context or prerequisites.

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/Lunar-Software-Solution/qbo-mcp-multicompany'

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