Skip to main content
Glama

list_customers

Retrieve a list of customers with optional filtering by status, search term, sorting, and pagination. Include related data like subscriptions, invoices, and payment methods.

Instructions

List customers with optional query parameters for filtering and pagination. GET /customers. See https://apiguide.rebillia.com/ for the Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
itemPerPageNoItems per page (default: 25, max 250)
queryNoSearch term: matches firstName, lastName, email, and related company name/support pin
statusNoFilter by customer status: active, disabled, or archived
sortByNoSort direction: ASC or DESC (default: ASC for customers)
orderByNoColumn to sort by (e.g. firstName, lastName, email, createdAt). Default: firstName
includeNoComma-separated includes: addressbook, paymentmethod, lastInvoice, subscriptions, unpaidInvoices, externalCustomers
filterIdNoOptional saved filter ID to apply predefined filters
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions optional query parameters but does not disclose pagination behavior, rate limits, authentication requirements, or idempotency. The generic API guide link does not compensate for missing details.

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 very concise, with two sentences covering the core action and providing an external reference. It is front-loaded with the essential information. Could be slightly more structured but is effective.

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

Completeness2/5

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

Given no output schema and no annotations, the description should explain what the tool returns (e.g., a list of customer objects with pagination metadata). It does not mention the response structure, error handling, or any limitations. This leaves the agent with incomplete context for invoking and interpreting results.

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 coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema comments; it merely restates that there are optional query parameters. The schema itself fully documents each parameter, so the description does not need to repeat, but also does not add value.

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 clearly states the verb 'List' and the resource 'customers', and mentions optional query parameters for filtering and pagination. It is specific enough to understand the tool's basic function, though it does not distinguish it from sibling list tools.

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?

The description provides no guidance on when to use this tool versus alternatives like list_customer_addresses or list_invoices. It only gives a link to the API guide without specific context. This is insufficient for an agent to decide between similar listing tools.

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/rhinosaas/rebillia-mcp-server'

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