Skip to main content
Glama
Mgabr90

Zoho CRM + Books MCP Server

by Mgabr90

books_get_customers

Retrieve customer lists from Zoho Books with filtering and pagination. Use as a starting point for invoicing and payment workflows.

Instructions

Get customer list from Books with filtering and pagination. WORKFLOW STARTER for Books financial operations.\n\nPrerequisites: Books access with customer management permissions\n\nNext Steps:\n→ Use books_get_customer for detailed customer information\n→ Use customer_id in books_create_invoice for billing\n→ Use customer_id in books_create_payment for payment processing\n\nCommon Financial Workflow: books_get_customers → books_get_customer → books_create_invoice → books_create_payment\n\nExample: Find customers by name\n{"search_text": "John", "per_page": 10}\n\nError Recovery: If no customers found, verify search filters and Books access permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (starts at 1)
emailNoFilter by email address (partial match)
phoneNoFilter by phone number (partial match)
addressNoFilter by address (partial match)
per_pageNoNumber of customers per page (1-200)
filter_byNoAdvanced filter field (e.g., "Status.Active", "CustomerType.Business")
last_nameNoFilter by last name (partial match)
first_nameNoFilter by first name (partial match)
sort_orderNoSort order: A=ascending, D=descending
search_textNoGlobal search across all customer fields
sort_columnNoColumn to sort by (e.g., "contact_name", "company_name", "created_time")
company_nameNoFilter by company name (partial match)
contact_nameNoFilter by contact name (partial match)
contact_typeNoFilter by contact type
customer_sub_typeNoFilter by customer subtype
Behavior4/5

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

The description adds context beyond the schema hints by noting it is a workflow starter, listing prerequisites, and providing error recovery advice. It clarifies that it is a list operation with filtering/pagination but does not detail rate limits or exact return behavior. Since no annotations are provided, the description carries reasonable burden and meets it well.

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-structured with bold headers for Prerequisites, Next Steps, Workflow, Example, and Error Recovery. Each section is succinct and purposeful; no waste. It remains readable despite its length, and the use of arrows improves scannability.

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 15 optional parameters and no output schema, the description effectively provides workflow context, an example, and error handling. It lacks explicit details about the return structure (e.g., pagination metadata), but the tool's role as a list starter is well covered. This is slightly above average but not fully complete.

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?

The input schema covers 100% of parameters, so the baseline is 3. The description goes beyond by providing a concrete example using 'search_text' and 'per_page' and explaining the overall filtering/pagination concept. This adds practical meaning without duplicating schema details.

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 'Get customer list from Books with filtering and pagination', using a specific verb and resource. It also labels itself a 'WORKFLOW STARTER' and references the singular sibling tool 'books_get_customer' for detailed information, distinguishing itself from related tools.

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 provides explicit usage guidance: 'Prerequisites: Books access with customer management permissions', 'Next Steps' linking to other tools, and a 'Common Financial Workflow' chain. It also gives an example and error recovery instructions, making when-to-use and alternatives clear.

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