Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

ls_list_customers

Read-onlyIdempotent

Retrieve customers from LemonSqueezy, optionally filtered by store or email. Paginated results include page metadata for tracking current and total pages.

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. 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 declare read-only and idempotent behavior. The description adds value by explaining pagination and filter options without contradicting 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 concise sentences, front-loaded with the main action and immediate pagination detail, with no wasted words.

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?

Covers the essential aspects: listing, filtering, pagination. Lacks mention of authorization scope or why you'd choose this over other list tools, but adequate for a read-only list with good schema coverage.

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%, so the description adds minimal extra meaning beyond what the schema already provides, only reiterating filter options briefly.

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 customers with optional filters and pagination, distinguishing it from `ls_get_customer` (single) and other list tools by specifying the resource.

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?

It indicates when to use (listing customers with optional filters) and mentions pagination handling, but does not explicitly state when not to use or compare with sibling tools.

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