Frihet MCP Server

List Invoices

list_invoices

Read-onlyIdempotent

Retrieve a paginated list of invoices filtered by status, date range, client, or series. Returns newest invoices first with cursor or offset pagination.

Instructions

List all invoices with optional pagination and filters. Returns a paginated list sorted by issue date (newest first). Supports filtering by status (draft/sent/paid/overdue/cancelled) and date range. Example: status='paid', from='2026-01-01', to='2026-03-31', limit=20 / Lista facturas con paginacion y filtros opcionales. Soporta filtrado por estado y rango de fechas.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End date filter in ISO 8601 (YYYY-MM-DD) / Fecha fin
`from`	No	Start date filter in ISO 8601 (YYYY-MM-DD) / Fecha inicio
`after`	No	Cursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
`limit`	No	Max results per page (1-100, default 50) / Resultados por pagina
`fields`	No	Comma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver
`offset`	No	Number of results to skip / Resultados a saltar
`status`	No	Filter by invoice status / Filtrar por estado
`clientId`	No	Filter by client ID / Filtrar por ID de cliente
`seriesId`	No	Filter by invoice series ID / Filtrar por ID de serie

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.3Jul 22, 2026
Removedv1.16.3Jul 22, 2026
Addedv1.15.2Jul 18, 2026
Removedv1.15.2Jul 18, 2026
Changed3 schema fields changedv1.15.0Jul 11, 2026
- addedOutput schema / properties / data / items / properties / clientName / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / items / properties / clientName / type
```
Removed value: -"string"
```
- removedOutput schema / properties / data / items / required
```
Removed value: -[
-  "id",
-  "clientName",
-  "items"
-]
```

Changed8 schema fields changedv1.13.1Jun 17, 2026

addedInput schema / properties / after

Added value: +{
+  "description": "Cursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor",
+  "type": "string"
+}

addedInput schema / properties / clientId

Added value: +{
+  "description": "Filter by client ID / Filtrar por ID de cliente",
+  "type": "string"
+}

addedInput schema / properties / fields

Added value: +{
+  "description": "Comma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver",
+  "type": "string"
+}

addedInput schema / properties / from

Added value: +{
+  "description": "Start date filter in ISO 8601 (YYYY-MM-DD) / Fecha inicio",
+  "type": "string"
+}

addedInput schema / properties / seriesId

Added value: +{
+  "description": "Filter by invoice series ID / Filtrar por ID de serie",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Filter by invoice status / Filtrar por estado",
+  "enum": [
+    "draft",
+    "sent",
+    "paid",
+    "overdue",
+    "cancelled"
+  ],
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "End date filter in ISO 8601 (YYYY-MM-DD) / Fecha fin",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clientName": {
+            "type": "string"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "dueDate": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "issueDate": {
+            "type": "string"
+          },
+          "items": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "description": {
+                  "type": "string"
+                },
+                "quantity": {
+                  "type": "number"
+                },
+                "unitPrice": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "description",
+                "quantity",
+                "unitPrice"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "notes": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "taxRate": {
+            "type": "number"
+          },
+          "total": {
+            "type": "number"
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "clientName",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "nextCursor": {
+      "type": "string"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "data",
+    "total",
+    "limit",
+    "offset"
+  ],
+  "type": "object"
+}

First observedv1.1.0Mar 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds pagination behavior, sorting order, and filter support. Does not disclose limitations (e.g., global vs scoped) or pagination interaction. Adequate but not rich.

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?

Two concise English sentences front-loaded with purpose, then details and example. Bilingual addition is redundant but not harmful. No wasted words.

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?

With 9 parameters, description only highlights status and date range, ignoring clientId, seriesId, after, offset, fields. Missing key filter capabilities despite output schema existing. Incomplete for complexity.

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 detailed parameter descriptions. Description redundantly mentions status and date range filters but introduces no new semantics. Baseline of 3 is appropriate.

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?

Clearly states 'List all invoices with optional pagination and filters' and mentions sorting by issue date. Distinguishes from sibling search_invoices implicitly by being a broad listing, but does not explicitly differentiate. Example adds clarity.

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 vs alternatives like search_invoices. Does not specify scope (e.g., user/workspace limitations) or when not to use. The example shows usage but no context for decision.

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

Deploy Server