Patreon MCP Server and API by Cotlet

Export earnings in Patreon

patreon_export_earnings

Read-onlyIdempotent

Export earnings in the user's own Patreon account from ChatGPT, Claude or any AI agent. Returns how to do it in Patreon step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Patreon Cloud Browser. Patreon's official API: Patreon has a public API v2, but it reads campaigns, members and posts and cannot create posts, message members or edit tiers (checked 11 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patreon_export_earnings"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the return content (screens, buttons, fields) and the important side-effect fact that it 'opens nothing by itself'. The API-v2 note adds useful context about why a browser workflow is required. Minor gap: no statement about how long or structured the returned steps are.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is front-loaded and clear, but the final API-v2 sentence spends words on capabilities irrelevant to earnings export (creating posts, messaging members, editing tiers). That tangent costs space without helping the agent invoke this tool.

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 no parameters and no output schema, the description does the necessary work: it says what is returned and what tool chain follows. A brief note on output format or typical step length would make it fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the description has no parameter semantics to carry; the schema and empty-properties object make that unambiguous. Baseline of 4 applies for a no-parameter tool.

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 concrete verb and resource ('Export earnings in the user's own Patreon account') and clarifies the deliverable is step-by-step instructions rather than an actual export ('Returns how to do it ... and opens nothing by itself'). It does not distinguish itself from the generic cotlet_app_guide sibling, so an agent must infer that difference.

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?

Gives an explicit follow-on path: use cotlet_browser_* tools in the user's Patreon Cloud Browser after receiving the steps. It also explains why the official API path is unavailable, implicitly steering away from an API route, but it never states when NOT to use this tool or names the alternative guide tool.

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

All Patreon MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?