QuickBooks Online MCP Server

delete_deposit

Deletes a QuickBooks Online deposit by ID or entity reference to remove outdated or incorrect deposit records.

Instructions

Delete a deposit 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": "delete_deposit"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It signals a destructive mutation by using "Delete," but does not disclose irreversibility, required permissions, side effects on linked transactions, or what the operation returns.

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 front-loaded sentence with no filler or repetition. Its brevity is not a conciseness defect, though the missing detail is reflected in the completeness and behavior dimensions.

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?

For a delete mutation with no annotations, no output schema, and a completely undocumented nested parameter, the description is insufficient. An agent cannot determine how to identify the deposit or what happens when it is deleted.

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?

The sole required parameter, idOrEntity, has 0% schema description coverage and is an empty nested object with additionalProperties. The description does not explain whether the caller must provide an ID, a full entity object, or a specific format, so it adds no parameter meaning beyond what the schema leaves opaque.

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, "Delete," and a specific resource, "deposit," plus the QuickBooks Online context. It is clearly distinguishable from create_deposit, get_deposit, update_deposit, and search_deposits by name, though it does not explicitly differentiate itself from those siblings.

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?

Provides no guidance on when to use this tool versus get_deposit, update_deposit, or search_deposits. It also omits prerequisites, when-not-to-use conditions, and any mention of confirmation or permanence.

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

Deploy Server