Skip to main content
Glama
Mgabr90

Zoho CRM + Books MCP Server

by Mgabr90

books_create_invoice

Create a new invoice in Zoho Books to bill customers. Provide customer ID and line items to generate an accurate bill.

Instructions

Create a new invoice in Books for billing customers. KEY FINANCIAL OPERATION in the Books workflow.\n\nPrerequisites:\n→ Use books_get_customers first to find target customer\n→ Use books_get_items to discover available products/services for line items\n→ Have valid customer_id from customer discovery\n\nNext Steps:\n→ Use books_create_payment to record payment against the invoice\n→ Use books_get_invoice to verify invoice creation\n→ Use invoice_id for payment tracking and reporting\n\nComplete Billing Workflow: books_get_customers → books_get_items → books_create_invoice → books_create_payment\n\nError Recovery: If creation fails, verify customer_id exists and line_items are properly formatted

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
termsNo
discountNo
due_dateNo
adjustmentNo
line_itemsYes
customer_idYes
template_idNo
invoice_dateNo
currency_codeNo
discount_typeNo
payment_termsNo
invoice_numberNo
salesperson_idNo
shipping_chargeNo
is_inclusive_taxNo
reference_numberNo
payment_terms_labelNo
adjustment_descriptionNo
is_discount_before_taxNo
Behavior5/5

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

Annotations indicate a write operation (readOnly=false) and non-idempotent behavior. The description adds valuable behavioral context by labeling it a 'KEY FINANCIAL OPERATION,' offering error recovery steps, and advising verification of customer_id and line_items. This goes beyond annotations with actionable operational details.

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 well-organized with clear sections (Prerequisites, Next Steps, Complete Billing Workflow, Error Recovery) and uses concise arrows and bold formatting. Every sentence contributes meaningful information, making it efficient and easy to scan.

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?

Given the complexity (20 parameters, no output schema), the description provides strong workflow context and prerequisites, and implies the response includes invoice_id. However, it does not explicitly describe the return value structure or address many optional parameters, leaving some ambiguity for a complex create operation.

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%, so the description must compensate. It only clarifies the two required parameters (customer_id and line_items) in the context of prerequisites and error recovery. The other 18 parameters (e.g., discount, due_date, payment_terms) receive no explanation or guidance, leaving a significant gap for an agent.

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 and resource: 'Create a new invoice in Books for billing customers.' This distinguishes it from sibling tools like books_create_estimate or books_create_bill, and the workflow context reinforces its specific role.

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

Usage Guidelines5/5

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

The description explicitly provides prerequisites (use books_get_customers and books_get_items), next steps (books_create_payment, books_get_invoice), and a complete billing workflow. This offers clear when-to-use guidance and alternatives, going beyond simple context.

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