Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs

ls_list_subscriptions

Read-onlyIdempotent

Retrieve and filter subscriptions by store, order, product, variant, or status. Paginated results with page metadata.

Instructions

List all subscriptions, optionally filtered by store, order, product, variant, or status. Results are paginated — check meta.page in the response for currentPage, lastPage, and total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storeIdNoFilter by store ID
orderIdNoFilter by order ID
orderItemIdNoFilter by order item ID
productIdNoFilter by product ID
variantIdNoFilter by variant ID
userEmailNoFilter by user email
statusNoFilter by subscription status
includeNoComma-separated related resources to include (e.g. 'store,customer,order,order-item,product,variant')
pageNumberNoPage number (1-indexed)
pageSizeNoResults per page (1-100)
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds valuable details: results are paginated and how to navigate pages (check meta.page). No contradictions with 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?

Two sentences: first covers filtering options, second covers pagination. Extremely concise and front-loaded with essential information.

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?

Given 10 optional parameters and no output schema, the description covers the core functionality and pagination mechanics. It does not mention default page size or limits, but the schema provides boundaries. The description is sufficient for an agent to use the tool 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 clear descriptions. The description aggregates key filters (store, order, product, variant, status) and mentions pagination, providing high-level guidance that helps an agent choose parameters, adding value beyond the schema.

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', and distinguishes from sibling list tools by specifying the optional filters (store, order, product, variant, status) and pagination. The name also aligns with the purpose.

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 explicitly states the tool is for listing subscriptions with optional filters and pagination. It does not explicitly mention when not to use it or alternatives, but the context of sibling tools makes it clear that this is the dedicated list tool for subscriptions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YawLabs/lemonsqueezy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server