Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ls_list_customers

Read-onlyIdempotent

Fetch customer lists from Lemon Squeezy, filtering by store ID or email. Use pagination parameters to navigate results.

Instructions

List all customers, optionally filtered by store or email. Results are paginated — check meta.page in the response for currentPage, lastPage, and total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoFilter by customer email
includeNoComma-separated related resources to include (e.g. 'store,orders,subscriptions,license-keys')
storeIdNoFilter by store ID
pageSizeNoResults per page (1-100)
pageNumberNoPage number (1-indexed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.2
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv0.10.10

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds a valuable behavioral detail: 'Results are paginated — check meta.page in the response for currentPage, lastPage, and total.' This goes beyond the annotations and informs the agent about response navigation.

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, zero waste. The primary action is front-loaded, and the pagination note is succinct and relevant. Every word earns its place.

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 definition is complete for a list tool: annotations cover safety, schema covers parameters, and the description covers pagination behavior. It doesn't mention default sorting or response fields beyond meta.page, but that's a minor gap given the simplicity of the operation.

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 coverage is 100% with descriptions for all five parameters. The description only reiterates the filters (store/email) and pagination, adding minimal new meaning beyond what the schema provides. The baseline of 3 is appropriate because the schema handles parameter documentation.

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 states a specific verb ('List'), a clear resource ('all customers'), and optional filters ('by store or email'), which distinguishes it from sibling tools like ls_get_customer (single retrieval) and ls_create_customer. It is unambiguous and not a tautology.

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 clearly conveys when to use it: to list all customers, optionally filtered. It implies a contrast with ls_get_customer for single-record retrieval, though it doesn't explicitly name alternatives. The context is clear enough for an agent to choose it for list operations.

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

Deploy Server

Other Tools