Skip to main content
Glama

List documents

easybill_list_documents
Read-onlyIdempotent

Retrieve easybill documents with filters for type, date, customer, and status, including pagination to access invoices, offers, credit notes, reminders, deliveries, and orders.

Instructions

List documents from easybill with optional filters and pagination.

Covers every document type: invoices, offers, credit notes, reminders, deliveries, orders.

NOT the right tool for: finding out whether a customer exists (use easybill_find_customer), or orienting yourself before creating a document (see easybill_create_document). Only call this when you actually need to read existing documents, and always with a filter.

Common recipes:

  • Unpaid invoices: type='INVOICE', paid_at='null'

  • Revenue in a period: type='INVOICE', document_date='2025-01-01,2025-12-31'

  • A customer's history: customer_id=

  • Exclude drafts: is_draft='0' - exclude cancelled: cancel_id='null'

Returns a compact field set by default; pass 'fields' for specific columns or ['all'] for everything.

Returns: { total, count, page, pages, has_more, next_page, items[] }. Use 'next_page' to continue paging. Monetary values are integers in cents (150 = 1.50 EUR).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Use 'next_page' from a previous response to continue.
typeNoFilter by document type. One of INVOICE, RECURRING, CREDIT, OFFER, REMINDER, DUNNING, STORNO, STORNO_CREDIT, DELIVERY, PDF, CHARGE, CHARGE_CONFIRM, LETTER, ORDER, PROFORMA_INVOICE, STORNO_PROFORMA_INVOICE, or several comma-separated (e.g. 'INVOICE,CREDIT').
limitNoItems per page, 1-1000 (default 25). Keep this small unless you need bulk data.
titleNoFilter by document title.
fieldsNoLimit returned columns to these field names (e.g. ['number','amount','paid_at']). Pass ['all'] for every field. Omit for a compact default set. Fewer fields = less context used.
numberNoFilter by document number (the official invoice number). Accepts one value or a list of values.
ref_idNoFilter by reference ID.
statusNoFilter by status (ACCEPT, DONE, DROPSHIPPING, CANCEL). Not all types have one.
paid_atNoFilter by payment date. Single date 'YYYY-MM-DD' or an inclusive range 'YYYY-MM-DD,YYYY-MM-DD'. Use the literal string 'null' to find all UNPAID documents.
is_draftNo'0' = only completed documents, '1' = only drafts.
cancel_idNoFilter by the ID of the cancelling document. Use the literal string 'null' for all documents that are NOT cancelled. Accepts one value or a list of values.
edited_atNoFilter by last edit date. Single date 'YYYY-MM-DD' or an inclusive range 'YYYY-MM-DD,YYYY-MM-DD'
is_archiveNo'0' = not archived, '1' = archived only.
project_idNoFilter by project ID. Accepts one value or a list of values.
customer_idNoFilter by customer ID. Accepts one value or a list of values.
vat_countryNoFilter by VAT country (ISO 2-letter code).
document_dateNoFilter by document date. Single date 'YYYY-MM-DD' or an inclusive range 'YYYY-MM-DD,YYYY-MM-DD'
response_formatNoOutput format: 'markdown' for readable prose, 'json' for machine-readable datamarkdown
shipping_countryNoFilter by shipping country (ISO code).
fulfillment_countryNoFilter by fulfillment country (ISO code).
Behavior5/5

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

Despite annotations already declaring readOnlyHint and idempotentHint, the description adds valuable behavioral details: compact default field set, pagination response shape with next_page, monetary values in cents, and the 'always with a filter' recommendation. This goes well beyond the annotations to explain actual 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?

The description is longer than average but every section earns its place: purpose, coverage, exclusions, recipes, return format, and monitoring units. It is well-structured and front-loaded with the core purpose, making it easy to scan.

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

Completeness5/5

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

For a tool with 20 parameters and no output schema, the description is remarkably complete. It explains the response envelope, pagination, default/compact fields, monetary units, and even mentions 'always with a filter' to prevent unbounded queries. This fully equips an agent to invoke the tool correctly.

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 schema already covers all 20 parameters with detailed descriptions (100% coverage), so the baseline is 3. The description adds extra value through common recipes (e.g., paid_at='null' for unpaid) and guidance on limiting output via the 'fields' parameter to save context, which helps select appropriate parameter values.

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 immediately states 'List documents from easybill with optional filters and pagination', which is a specific verb+resource+scope. It also distinguishes from siblings by covering every document type and explicitly contrasting with easybill_find_customer and easybill_create_document.

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 says 'NOT the right tool for' customer lookup or pre-creation orientation, and tells when to use it: 'Only call this when you actually need to read existing documents, and always with a filter.' It also provides common recipes for common use cases, giving clear when-to-use and when-not-to-use guidance.

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/stack74/easybill-mcp'

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