Skip to main content
Glama

Chargebee

by io.github.pipeworx-io

Chargebee List Subscriptions

chargebee_list_subscriptions
Read-onlyIdempotent

List all subscriptions with optional filtering by status (e.g., 'active', 'cancelled'). Returns subscription IDs, plans, amounts, and renewal dates. Paginate with limit and offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_siteYesChargebee site name (e.g., "mycompany" for mycompany.chargebee.com)
limitNoNumber of results to return (default 10, max 100)
offsetNoPagination offset from a previous response
statusNoFilter by subscription status: active, cancelled, non_renewing, future, in_trial, paused
_apiKeyYesChargebee API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYesArray of subscription objects
next_offsetNoPagination offset for next page of results

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "list": {
+      "description": "Array of subscription objects",
+      "items": {
+        "properties": {
+          "subscription": {
+            "description": "Subscription details",
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_offset": {
+      "description": "Pagination offset for next page of results",
+      "type": "string"
+    }
+  },
+  "required": [
+    "list"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-chargebee-api-key",
+    "_site": "mycompany",
+    "limit": 25,
+    "status": "active"
+  },
+  {
+    "_apiKey": "your-chargebee-api-key",
+    "_site": "mycompany",
+    "limit": 50,
+    "offset": "eyJkaXJlY3Rpb24iOiJuZXh0IiwiY3Vyc29yIjoiMjAyMy0wMS0wMVQwMDowMDowMFoifQ==",
+    "status": "cancelled"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by specifying the return fields (subscription IDs, plans, amounts, renewal dates) and pagination mechanism (limit and offset), providing behavioral context beyond annotations.

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, no redundant words, and front-loads the core purpose. Every sentence adds necessary detail without extraneous content.

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?

Given the tool's moderate complexity (5 documented parameters, output schema exists), the description covers purpose, filtering, return fields, and pagination. Authentication is handled via parameters. It is complete for an AI agent to use 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?

Schema coverage is 100% with all parameters described. The description reinforces parameter usage: 'optional filtering by status' clarifies the 'status' parameter's role, and 'paginate with limit and offset' adds context beyond the schema's basic descriptions.

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' and resource 'subscriptions', with optional status filtering and specific return fields (IDs, plans, amounts, renewal dates). It distinguishes from sibling tools like 'chargebee_get_subscription' which retrieves a single subscription, and 'chargebee_list_customers' which is for a different entity.

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 provides clear context for when to use the tool: listing subscriptions with optional filtering and pagination. However, it does not explicitly exclude scenarios or mention alternatives like 'chargebee_get_subscription' for single subscriptions.

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

All Chargebee toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation1/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all answer questions or discover data via the same routing engine, with ask_pipeworx_beta explicitly stated to be identical to ask_pipeworx. Polymarket tools (arbitrage, edges, edge_tracker, fill_risk) also blur together, and ai_visibility_check overlaps with scan_competitor_ai_presence.

Naming Consistency2/5

Some clusters are consistent (chargebee_list_*/chargebee_get_*, polymarket_*, pipeworx_*), but the set mixes snake_case with varying verb styles and many unprefixed tools (remember, recall, forget, subscribe, unsubscribe, validate_claim). The 5 Chargebee tools use a clean prefix while the other 31 tools follow several different conventions, making the overall pattern unpredictable.

Tool Count2/5

36 tools is excessively heavy for a server named Chargebee, especially since only 5 tools actually relate to Chargebee. The remaining 31 tools form a broad Pipeworx/prediction-market/utility toolkit that has little connection to the server's apparent billing purpose, making the count feel bloated and unfocused.

Completeness1/5

The Chargebee-specific surface is severely incomplete: it only supports reading customers, subscriptions, and invoices, with no create, update, delete, payment, dunning, coupon, or plan-management operations. The rest of the tools belong to unrelated domains, so the set as a whole has no coherent lifecycle coverage and would leave agents unable to perform even basic Chargebee management tasks.

Resources