Skip to main content
Glama
Sign In

Patreon MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Send message to patron in Patreon

patreon_send_message_to_patron
Read-onlyIdempotent

Send message to patron 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_send_message_to_patron"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotent and non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: the tool opens nothing itself, returns step-by-step screens/buttons/fields guidance, and must be followed by browser tool calls — exactly the non-obvious trait an agent needs.

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 behavior is front-loaded in one dense sentence, but the trailing API-v2 justification is lengthy and includes an oddly specific dated parenthetical ('checked 11 Oct 2026') that reads as padding rather than operational guidance.

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 output schema, the description carries the return-value burden and does so by describing the step-by-step guide format. Remaining gap: no statement of how the target patron is identified when the schema has no parameters.

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?

Zero parameters, so the baseline is 4. The description doesn't explain how the patron and message content are conveyed given an empty schema, but there is nothing in the schema to expand on.

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?

The description states a specific verb and resource (send message to a patron in Patreon) and immediately clarifies that the tool only returns instructions rather than performing the send. That distinction is crucial and well front-loaded, though the name alone would mislead without it.

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 explicitly routes the agent to the cotlet_browser_* tools after using this one, and explains why Patreon's official API cannot be used instead (no message/create capability). It doesn't mention preconditions such as needing an authenticated Patreon Cloud Browser session before the follow-up browser steps.

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 toolsInspect
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