list_merchant_programs

Retrieve paginated affiliate programs for your authenticated merchant account. Access campaign details, commission structures, and program data with cursor-based navigation.

Instructions

List affiliate programs belonging to the authenticated merchant (identified by SYNDICATE_MERCHANT_KEY). Returns the API response shape { data, cursor, hasMore } where data is the current page of programs and cursor is the value to pass back for the next page when hasMore is true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cursor`	No	Pagination cursor returned by a previous call (`cursor` field). Omit for the first page.
`limit`	No	Maximum number of programs to return (1–100). Defaults to 20.

Tool Definition Quality

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and successfully discloses the authentication mechanism (SYNDICATE_MERCHANT_KEY), the paginated response structure (data/cursor/hasMore), and the pagination protocol. It does not explicitly state that this is a read-only operation, though implied by the verb 'List'.

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?

The description consists of two efficient sentences: the first establishes purpose and auth context, the second details the response structure and pagination behavior. Every sentence delivers distinct value with no redundancy.

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 the absence of an output schema, the description appropriately documents the return shape and pagination mechanics. It successfully covers the tool's low complexity (2 simple parameters) and explains the merchant authentication context, leaving no critical gaps for invocation.

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 the schema fully documents both 'cursor' and 'limit' parameters. The description does not add parameter-specific semantics beyond what the schema provides, meeting the baseline expectation for high-coverage schemas.

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 opens with the specific verb 'List' followed by the resource 'affiliate programs' and scope 'belonging to the authenticated merchant', clearly distinguishing it from siblings like 'search_programs' (which implies broader filtering) and 'get_program_details' (single item retrieval).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description clarifies this lists programs for the authenticated merchant (implied by SYNDICATE_MERCHANT_KEY), it does not explicitly state when to use this tool versus 'search_programs' or 'get_program_details', nor does it mention prerequisites beyond the implicit authentication requirement.

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

Install Server

syndicate-links-mcp