Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ls_list_affiliates

Read-onlyIdempotent

List affiliates across your Lemon Squeezy stores with optional email filtering and pagination. Returns affiliate details from every store the API key can access.

Instructions

List all affiliates for the authenticated user's stores, optionally filtered by user email. Results are paginated — check meta.page in the response for currentPage, lastPage, and total. Cross-store note: LEMONSQUEEZY_ALLOWED_STORE_IDS does NOT gate this tool -- it has no storeId field and no parent ID filter to scope by, so it returns affiliates tied to every store the API key can see, including non-allowed ones. Pair with a scoped LemonSqueezy API key for true cross-store enforcement -- the API key's visibility is the true boundary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoComma-separated related resources to include (e.g. 'store,user')
pageSizeNoResults per page (1-100)
userEmailNoFilter by affiliate's user email
pageNumberNoPage number (1-indexed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.2
    • changedInput schema / properties / userEmail / 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.7/5.0
Behavior5/5

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

Exceeds annotations by disclosing pagination structure (meta.page currentPage, lastPage, total), the absence of storeId scoping, and that results are bound to API key visibility. These are critical behavioral traits not covered by readOnlyHint, openWorldHint, idempotentHint, or destructiveHint. No contradiction 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?

Three dense sentences, front-loaded with the core purpose, then pagination, then the critical cross-store caveat. Every sentence adds distinct value; the caveat is lengthy but essential due to the tool's non-obvious scoping behavior. No filler.

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 list tool with no output schema, the description covers essential invocation details: scope, optional email filter, pagination response format, and a significant behavioral gotcha. Nothing an agent needs to call the tool correctly is missing.

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 already documents all four parameters with 100% coverage, so baseline is 3. The description only restates the userEmail filter and pagination behavior, adding no new parameter-level meaning beyond what the schema provides.

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?

States a specific verb and resource ('List all affiliates') with clear scope ('for the authenticated user's stores') and optional filter ('by user email'). The description is clearly distinct from sibling ls_get_affiliate (singular vs. list) and other list tools, and the pagination note reinforces its list nature.

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?

Provides explicit usage context: when to use the tool (list all affiliates, optionally filtered by email) and a when-not warning that LEMONSQUEEZY_ALLOWED_STORE_IDS does not gate this tool, recommending a scoped API key for true store enforcement. This acts as a clear exclusion and guidance for correct usage, even without naming an alternative sibling.

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