xendit-mcp

list_invoices

Read-only

Retrieve invoices from Xendit with filters for status, currency, creation date range, and pagination.

Instructions

List invoices from your Xendit account with optional filters for status, date range, and pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_invoices"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of invoices to return (1-100)
`status`	No	Filter by invoice status
`currency`	No	Filter by currency (IDR, PHP, etc.)
`createdAfter`	No	Return invoices created after this ISO 8601 timestamp. Must be used with createdBefore.
`createdBefore`	No	Return invoices created before this ISO 8601 timestamp. Must be used with createdAfter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0May 25, 2026

changedInput schema / properties / createdAfter / description

Previous value: -"Return invoices created after this date (ISO 8601, e.g., 2025-01-01T00:00:00Z)"New value: +"Return invoices created after this ISO 8601 timestamp. Must be used with createdBefore."

changedInput schema / properties / createdBefore / description

Previous value: -"Return invoices created before this date (ISO 8601)"New value: +"Return invoices created before this ISO 8601 timestamp. Must be used with createdAfter."

First observedv1.0.0Apr 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and description confirms read-only listing. Adds filter context but does not explain pagination mechanics or result set behavior.

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?

Single sentence, 16 words, no redundant information. Front-loaded with verb and resource.

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?

Covers basic listing and filters. Missing details on pagination and return format, but for a simple tool with no output schema, it is sufficiently complete.

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% with descriptions for all 5 parameters. Description groups filters but adds no extra meaning beyond the schema.

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?

Clearly states it lists invoices from Xendit account with optional filters, distinguishing it from sibling get_invoice (single invoice) and list_transactions (different resource).

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?

Lacks explicit guidance on when to use this tool versus alternatives like get_invoice or list_transactions. No exclusions or when-not-to-use context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server