Skip to main content
Glama
Mgabr90

Zoho CRM + Books MCP Server

by Mgabr90

books_create_item

Create a new product or service item in Zoho Books inventory for selling goods, offering services, or adding to invoices, with SKU, rate, unit, and tax details.

Instructions

Create a new product or service item in Books inventory. Use for adding products to sell, services to offer, or items to include in invoices.

Example: Create service item {"name": "Consulting Services", "description": "Business consulting", "rate": 150, "unit": "hrs", "item_type": "sales"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoStock Keeping Unit (SKU) code
nameYesItem name or product title
rateNoItem price or rate
unitNoUnit of measure (e.g., "pcs", "hrs", "kg")
tax_idNoTax ID if item is taxable
item_typeNoItem type (e.g., "sales", "purchases", "sales_and_purchases")
is_taxableNoWhether item is subject to tax
descriptionNoDetailed item description
product_typeNoProduct type (e.g., "goods", "service")
Behavior2/5

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

The description mentions creation but lacks details on side effects, required permissions, idempotency, or error behavior. With no annotations, the description fails to disclose any behavioral traits beyond the basic creation action.

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

Conciseness5/5

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

The description is short and front-loaded, with a clear purpose and an illustrative example. No redundant wording.

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

Completeness3/5

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

The description gives a solid overview and example, but with 9 parameters, no output schema, and no annotations, it leaves gaps such as response format, error handling, and all parameter combinations. Not fully complete for a complex tool.

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

Parameters4/5

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

All 9 parameters are already described in the schema (100% coverage). The description adds value by providing a concrete JSON example that demonstrates usage of name, description, rate, unit, and item_type, making the parameter semantics more concrete.

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 verb 'Create' and the resource 'a new product or service item in Books inventory.' It further specifies use cases (products to sell, services to offer, invoice items) and includes an example, distinguishing it from sibling create tools like books_create_customer.

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

Usage Guidelines4/5

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

It provides explicit 'Use for' guidance listing three specific scenarios. It doesn't explicitly contrast with alternatives (e.g., books_update_item) or state when not to use, but the context is clear enough for an AI agent to select appropriately.

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/Mgabr90/zoho-mcp-server'

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