patreonmcp

list_members

Read-onlyIdempotent

Fetch paginated patron lists for a Patreon campaign, with cursor pagination and optional fields like user profile, email, tiers, address, or private notes.

Instructions

List patrons for a campaign with cursor pagination.

Input Schema

Name	Required	Description
`cursor`	No	next_cursor from a previous list_members call.
`page_size`	No	Results per page (1-1000).
`campaign_id`	No	Campaign ID. Omit only when the token can see exactly one campaign.
`include_note`	No	Include the creator's private note about each patron.
`include_user`	No	Include the patron's public user profile.
`include_email`	No	Include patron email addresses. Requires PATREON_ALLOW_PII=1 and the campaigns.members[email] scope; patrons may hide it.
`include_tiers`	No	Include the tiers each member is entitled to.
`include_address`	No	Include shipping addresses. Requires PATREON_ALLOW_PII=1 and the campaigns.members.address scope; handle as sensitive data.

Output Schema

Name	Required	Description	Default
`total`	No
`members`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and idempotency profile is covered. The description usefully adds that pagination is cursor-based, but says nothing about default page size behavior, ordering, or rate limits beyond what the schema provides.

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?

A single ten-word sentence with zero filler, front-loading the resource and the pagination model. Nothing redundant or buried.

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?

With a rich 8-parameter schema at 100% coverage and an output schema present, the description needn't explain returns or filters. The one thing worth flagging at this level — pagination — is stated. It is complete enough for correct invocation, though it could note ordering or the PII-sensitive nature of some includes.

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 every parameter including cursor, page_size, and the include_* PII flags is fully documented in the schema. The description only echoes the cursor-pagination concept, adding no meaning beyond the structured fields. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('patrons for a campaign'), and adds the pagination model ('cursor pagination'). It does not name or distinguish itself from siblings like get_member or list_campaigns, so an agent must infer the distinction from the plural resource alone.

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

Usage Guidelines2/5

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

No when-to-use guidance is given in the description. It never states when to reach for this instead of get_member (single patron) or list_campaigns, nor any prerequisites; the only conditional guidance lives in the schema's campaign_id description, not here.

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