billingo-mcp

List products

billingo_list_products

Read-onlyIdempotent

Retrieve products and services from the Billingo catalogue with paging and free-text name search. Use it to find catalogue items by keyword or browse results page by page.

Instructions

Lists products and services from the product catalogue.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`query`	No	Free-text search over the product name.
`per_page`	No	Results per page (1-100, default 25).

Output Schema

Name	Required	Description	Default
`data`	Yes
`total`	No
`per_page`	No
`last_page`	No
`current_page`	No
`next_page_url`	No
`prev_page_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.3Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "current_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "comment": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "currency": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ean": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "gross_unit_price": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "net_unit_price": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "sku": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unit": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "vat": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "last_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "next_page_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "per_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "prev_page_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond the purpose statement, such as pagination behavior, search semantics, or catalogue scope details.

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 a single front-loaded sentence with no wasted language. It immediately communicates the tool's resource and scope.

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?

This is a low-complexity list operation, and the schema, annotations, and output schema already cover parameters, safety, and return values. The description is sufficient for correct invocation, though it could mention search or pagination to be fully self-contained.

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 description coverage is 100%, so the schema already documents page, query, and per_page clearly. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 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?

The description uses a specific verb and resource: 'Lists products and services from the product catalogue.' It is clear what the tool does, though it does not explicitly distinguish this listing tool from sibling retrieval tools like billingo_get_product.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by 'Lists products and services from the product catalogue,' but there is no explicit guidance on when to use this versus billingo_get_product or billingo_get_product_quantity, nor any stated prerequisites or exclusions.

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