Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

listCustomers

listCustomers

Retrieve a paginated list of customers with options to search, filter by ID, email, phone, or status, and control sorting.

Instructions

Retrieve a paginated list of customers, with options for searching, filtering by ID, external ID, email, phone number, communication status, auto-charge status, creation date, customer name, and business entity ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe cursor for pagination to fetch the next or previous set of records.
limitNoMaximum number of customers to return per page (defaults to 10).
searchNoAdvanced key-value search query. Format: 'field=value' or 'field1=value1,field2=value2'. Supports any customer field including nested JSON paths. Examples: 'customer_name=Acme', 'email=john@example.com', 'customer_name=Acme,external_id=EXT-100', 'custom_data.users=abc@dev.in'. String fields use case-insensitive contains matching. Do NOT pass plain text — always use field=value format.
search_name_external_idNoQuick relevance-ranked search across customer_name and external_id. Accepts plain text (e.g., 'Acme'). Results are ranked: exact match first, then starts-with, then contains. Simpler alternative to the 'search' parameter when you only need to find customers by name or external ID.
orderNoOrder of results (e.g., '-created_at' for descending creation date).-created_at
sort_keyNoKey to sort the results by (e.g., 'id').
sort_typeNoSort order type (e.g., 'asc' for ascending).
expandNoFields to expand in the response (e.g., 'contacts').
idNoFilter by customer ID (exact match).
id__inNoFilter by a comma-separated list of customer IDs.
external_idNoFilter by external ID (exact match).
external_id__ilikeNoCase-insensitive partial match for external ID.
emailNoFilter by email (exact match).
email__ilikeNoCase-insensitive partial match for email.
phone_number__ilikeNoCase-insensitive partial match for phone number.
communications_enabledNoFilter by communications enabled status.
auto_charge_enabledNoFilter by auto-charge enabled status.
created_at__gteNoFilter by creation date greater than or equal to (ISO 8601 format).
created_at__lteNoFilter by creation date less than or equal to (ISO 8601 format).
customer_name__ilikeNoCase-insensitive partial match for customer name.
business_entity_idNoFilter by business entity ID (exact match).
invoice__customer_idNoFilter by invoice customer ID.
invoice__statusNoFilter by invoice status.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'paginated' but does not disclose pagination behavior (e.g., cursor vs offset, default limit), rate limits, auth requirements, or whether it is read-only. Lacks details on potential side effects.

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

Conciseness3/5

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

The description is a single long sentence that lists many filter options. It is not front-loaded with the most critical info (e.g., core functionality). Could be more concise by structuring or grouping filters.

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?

Given the complexity (24 parameters, no output schema), the description is adequate but incomplete. It covers filtering capabilities but lacks details on pagination, return format, error conditions, and behavior when no filters are applied.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description enumerates many filter fields but does not add meaning beyond the schema. No new semantic context is provided for any parameter.

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 action ('retrieve a paginated list') and the resource ('customers'), and distinguishes it from sibling tools by listing numerous filter options. It is specific and not a tautology.

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?

No guidance on when to use this tool vs alternatives (e.g., getCustomerById or other list tools). No mention of prerequisites or when not to use. The description only lists available filters without context for choosing between them.

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/zenskar/mcp-zenskar'

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