Skip to main content
Glama

lemonsqueezy

by io.usefulapi

List subscription invoices

lemonsqueezy_list_subscription_invoices
Read-only

List subscription invoices, optionally filtered by store, status, or refunded flag. API: GET /subscription-invoices (filter[store_id], filter[status], filter[refunded]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by invoice status (e.g. paid, void, refunded).
includeNoComma-separated related resources to sideload (JSON:API include=), e.g. 'store,variant'.
refundedNoFilter by refunded flag.
store_idNoFilter to a single store id.
page_sizeNoResults per page (JSON:API page[size], max 100). Default 10.
page_numberNoPage number (JSON:API page[number]). Default 1.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true. The description adds the filtering capability and API endpoint but does not disclose pagination behavior, response format, or any side effects. Little value 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence covering purpose and filters, plus API endpoint reference. Front-loaded and efficient, though the API detail could be formatted as a side note.

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?

No output schema exists, yet the description does not explain what the response contains (e.g., list of invoice objects, pagination details). For a tool with pagination parameters, this is a notable gap.

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 parameters are already documented. The description mentions three filters (store, status, refunded) but adds minimal extra context beyond the schema. 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 the action 'List subscription invoices' with optional filters. It uses a specific verb and resource, but does not differentiate from sibling list tools like list_subscriptions or list_orders.

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 tool versus alternatives such as list_subscriptions (which also lists invoices but with different scoping) or when filters are required. The description simply states it lists invoices without any usage context.

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

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

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (get vs list for each entity, plus specific write operations). Filtering parameters further distinguish list tools. No overlapping purposes.

Naming Consistency5/5

All tools follow a consistent `lemonsqueezy_action_resource` pattern using lowercase and underscores. Actions are consistently get, list, create, cancel, or update.

Tool Count5/5

18 tools cover a broad set of resources (customers, orders, stores, subscriptions, discounts, license keys, prices, products, invoices, variants, checkouts) for a comprehensive e-commerce platform. Each tool earns its place.

Completeness3/5

While reading (list/get) is well-covered for most resources, creation and deletion are missing for many core entities (customers, products, orders, etc.), which may force agents to rely on external processes. Only subscriptions and checkouts have write support.

Resources