Skip to main content
Glama

patreon_click

Clicks a numbered element on the current Patreon page, letting AI agents navigate and act on posts, tiers, and member controls by referencing element numbers from the last page read.

Instructions

Click a numbered element on the current Patreon page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "patreon_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether clicking navigates, submits a form, triggers irreversible side effects, or how failures (stale element numbers) are surfaced — all critical for a click action.

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

Conciseness4/5

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

One front-loaded sentence with no filler, and the key constraint ('current page') is prominent. It is appropriately sized but so terse that it edges toward under-specification rather than crispness.

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 one-parameter tool this covers the basic mechanics, but with no annotations and no output schema it should at least say what happens after the click and how element numbering relates to the prior read. That leaves a meaningful gap for an action tool.

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 coverage is 100% and the single parameter's description already ties the number to the last read. The description's 'numbered element' reinforces but adds no new meaning such as renumbering rules or staleness handling; 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 (click) and resource (numbered element on the current Patreon page), which is enough for an agent to know this is an interaction tool. It stops short of contrasting with siblings like patreon_type, but the verb alone largely separates it.

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 'current Patreon page' and 'element number from the last read' imply a read-then-click sequence, so usage is inferable. There is no explicit statement about when to click versus type or open, and no note on preconditions such as requiring a prior read.

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