Skip to main content
Glama

list_documents

List documents by type with filters for date, contact, and payment status to find specific invoices, receipts, or orders.

Instructions

List all documents of a specific type with optional filters for date range, contact, payment status, and sorting. Supports field filtering to reduce response size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docTypeYesType of document to list
pageNoPage number for pagination (optional)
limitNoMaximum number of items to return (default: 50, max: 500)
summaryNoReturn only count and pagination metadata without items (default: false)
starttmpNoStarting timestamp (Unix timestamp) for filtering documents by date
endtmpNoEnding timestamp (Unix timestamp) for filtering documents by date
contactidNoFilter documents by contact ID
paidNoFilter by payment status: 0=not paid, 1=paid, 2=partially paid
billedNoFilter by billed status: 0=not billed, 1=billed
sortNoSort order by creation date
fieldsNoSelect specific fields to return (e.g., ["id", "contactName", "total"]). Reduces response size by 70-90%. If not provided, returns default fields: id, contact, contactName, date, tax, total, status
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses field filtering and its performance benefit, but does not mention side effects, authorization requirements, or pagination behavior beyond what is in the schema. The tool appears read-only, but this is not explicitly stated.

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 two sentences, front-loads the core purpose, and includes only essential information. No wasted words.

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 11 parameters, 100% schema coverage, and no output schema, the description covers the core functionality and key filters. It lacks details on response structure, pagination limits (partially in schema), and error handling, but is adequate for a list tool with well-documented parameters.

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 all parameters are described in the schema. The description summarizes the filters but adds no new information beyond what is in the schema. Baseline 3 is appropriate.

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 verb 'List', the resource 'documents', and the scope 'of a specific type'. It also highlights optional filters and field filtering, distinguishing it from siblings like get_document (single document) and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists the available filters (date range, contact, payment status, sorting) and field filtering, making the usage context clear. However, it does not explicitly state when not to use this tool or mention alternative tools for specific needs.

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/iamsamuelfraga/mcp-holded'

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