Skip to main content
Glama

patreon_open

Opens a Patreon page in your signed-in Cloud Browser so you can work with creator posts, members, and tiers.

Instructions

Open a Patreon page in your signed-in Cloud Browser (default https://www.patreon.com) to work with creator posts, members and tiers.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.patreon.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal that the browser is signed in and that the default target is https://www.patreon.com, but it omits what 'open' actually does (new tab vs. navigate existing), whether prior page state is lost, authentication failure behavior, and what handle or result comes back. For an unannotated tool these gaps are significant.

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 sentence with zero filler, and the action and target are front-loaded before the optional parenthetical default.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity one-parameter tool this covers purpose and environment, but it leaves the agent unsure how the opened page relates to subsequent patreon_click/patreon_read/patreon_type calls and whether re-invocation reuses or replaces the current page.

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?

With one optional parameter and 100% schema description coverage, the schema already documents 'url' and its default. The description merely restates the same default, adding no format constraints, domain restrictions, or examples of valid Patreon sub-paths.

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 pairs the specific verb 'Open' with the resource 'a Patreon page' and the environment ('signed-in Cloud Browser'), which cleanly separates it from sibling operations like patreon_click, patreon_read, and patreon_type. It stops short of naming any sibling explicitly, so it lands at clear-but-not-differentiated-by-reference.

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?

The phrase 'to work with creator posts, members and tiers' hints at the context of use but never says when to call this versus patreon_read or patreon_status, nor whether it is a prerequisite for the interaction tools. Usage is implied rather than stated.

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