Skip to main content
Glama

recharge

by io.usefulapi

List subscriptions

recharge_list_subscriptions
Read-only

List subscriptions with optional filters (customer, address, status, ids, created/updated date ranges) and sorting. Returns { subscriptions }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /subscriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of subscription ids to fetch.
limitNoMax results per page (1-250, default 50).
cursorNoPagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests.
statusNoFilter by subscription status, e.g. active | cancelled | expired.
sort_byNoSort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc.
address_idNoFilter by address id.
customer_idNoFilter by customer id.
created_at_maxNoFilter to subscriptions created on/before this date (ISO 8601).
created_at_minNoFilter to subscriptions created on/after this date (ISO 8601).
updated_at_maxNoFilter to subscriptions updated on/before this date (ISO 8601).
updated_at_minNoFilter to subscriptions updated on/after this date (ISO 8601).

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, consistent with a listing operation. The description adds valuable behavioral context: cursor-based pagination with default/max limits, and the critical rule to omit filters when using cursor. This goes beyond what annotations convey.

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 concise (4 sentences), front-loads the purpose, and every sentence adds necessary information (filters, return shape, pagination rules, REST path). No wasted words.

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?

For a tool with 11 parameters and no output schema, the description covers key aspects: return object, pagination mechanics, filter types, sorting, and the API endpoint. It provides sufficient context for an agent to use it 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?

Input schema has 100% description coverage, so baseline is 3. The description adds value by grouping parameters (filters, pagination) and highlighting the cursor constraint, which is not fully captured in individual parameter 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 tool lists subscriptions with optional filters and returns the result object. The verb 'list' and resource 'subscriptions' are explicit, and it distinguishes itself from the singular 'recharge_get_subscription' sibling and other list tools.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use filters and pagination, including the crucial constraint that when using the 'cursor' parameter, only 'limit' can accompany it. This prevents common API errors and clarifies proper usage.

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

All recharge 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

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (e.g., activate vs cancel subscription, list vs get for each entity). No two tools have overlapping purposes.

Naming Consistency5/5

All tools follow a consistent pattern: recharge_<verb>_<resource> (e.g., recharge_get_subscription, recharge_list_charges). Verbs are uniform (get, list, activate, cancel, skip).

Tool Count5/5

15 tools cover essential read and mutation operations for subscriptions and charges, plus read-only for other entities. This is well-scoped without being excessive or insufficient.

Completeness2/5

The server lacks create, update, and delete operations for most resources (customers, addresses, orders, products, subscriptions). Only subscription activation/cancel and charge skip are mutations. This is a significant gap for a subscription management API.

Resources