Zoho CRM + Books MCP Server

books_update_item

Modify existing item records in Zoho Books, updating fields such as SKU, name, rate, unit, tax, and description.

Instructions

Update an existing item in Books

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": {
      "item_id": "<item_id>"
    },
    "name": "books_update_item"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	No
`name`	No
`rate`	No
`unit`	No
`tax_id`	No
`item_id`	Yes
`item_type`	No
`is_taxable`	No
`description`	No
`product_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It merely says 'Update', which implies mutation, but does not state whether the update is partial or full, whether unspecified fields are preserved, or any other side effects. This is a significant gap for an update operation with 10 parameters.

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 zero filler words. It is appropriately sized for its minimal content, though it could include more detail without becoming verbose.

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?

With 10 parameters, no annotations, no output schema, and no parameter descriptions, this bare-minimum description is completely inadequate. It provides no context about what data is returned, whether updates are partial, or any special considerations for updating a Books item.

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 0%, and the description does not explain any parameters. The parameter names in the schema (e.g., sku, rate, is_taxable) are self-explanatory, but the description adds no semantic value beyond what the property names already convey. It fails to compensate for the lack of schema documentation.

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?

The description 'Update an existing item in Books' clearly states the action (update) and the resource (item), distinguishing it from sibling tools like books_create_item and books_delete_item. However, it does not explicitly differentiate from other update tools (e.g., books_update_invoice), though the resource scope is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies when to use this tool (modifying an existing item), but there is no explicit guidance on when not to use it or mention of alternatives. It relies entirely on the name and the verb 'update' to convey usage context, which is minimally sufficient but not detailed.

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

Deploy Server