billingo-mcp

List partners

billingo_list_partners

Read-onlyIdempotent

Retrieve customers newest first with paging and free-text name search. Use page and per_page for pagination or query to find a partner by name.

Instructions

Lists partners (customers), newest first. Supports paging and a free-text search over the partner name.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`query`	No	Free-text search over the partner 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": {
+          "account_number": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "address": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "additionalProperties": {},
+                    "properties": {
+                      "address": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "city": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "country_code": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "post_code": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      }
+                    },
+                    "type": "object"
+                  },
+                  {
+                    "items": {},
+                    "maxItems": 0,
+                    "type": "array"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "emails": {
+            "anyOf": [
+              {
+                "items": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "type": "array"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "iban": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "phone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "swift": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tax_type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "taxcode": {
+            "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

A3.8/5.0

Behavior4/5

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

Annotations already mark this as read-only, idempotent, and open-world. Beyond that, the description discloses useful behavior: results are ordered newest first, paging is supported, and search is limited to partner name. It does not cover rate limits or response shape, but the output schema exists.

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?

Two short sentences, front-loaded with the operation and followed by key behavioral details. Every phrase earns its place, with no repetition or filler.

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?

The tool is simple, its parameters are fully documented in the schema, and an output schema exists. The description covers ordering, paging, and search scope. The only minor gap is explicit routing guidance relative to billingo_get_partner.

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 already 100%, with all three parameters fully documented. The description reinforces paging and free-text search over partner name, but adds no syntax, defaults, or constraints beyond what the schema provides. 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 clearly states a specific verb and resource: it lists partners (customers). It also adds useful distinctions such as 'newest first' and free-text search over partner name. It could more explicitly contrast with the sibling get_partner, but the plural list operation is clear.

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: this is the listing tool, and search/paging are supported. However, the description does not explicitly say when to use this versus billingo_get_partner or other retrieval siblings, nor does it mention exclusions or prerequisites.

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