Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

patreon_creator_tiers

Retrieve a Patreon creator's public membership tiers and published benefits by handle to compare support options, excluding member-only entitlements and member counts.

Instructions

Get a creator's public Patreon membership tiers. Returns published membership tiers and their published benefits from a creator's public Patreon page. It excludes member-only entitlements, tier capacity, and member counts. handle is the creator's page handle, e.g. CachyOS for patreon.com/CachyOS.

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": {
      "handle": "<handle>"
    },
    "name": "patreon_creator_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesCreator page handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are present, so the description must carry the transparency burden. It does so by clarifying this is a read of a creator's public page and by enumerating what is excluded (member-only entitlements, tier capacity, member counts). This is useful behavioral scoping beyond the schema.

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?

Three sentences, front-loaded with the action, then the what's-included/excluded clarification, then the handle example. It is not verbose, though the first two sentences overlap somewhat in terminology ('public' and 'published') without causing noise.

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 tells the agent this returns tiers and benefits while explicitly listing the omitted fields. For a one-parameter read-only tool, that is enough context to call it correctly.

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 schema only gives 'Creator page handle' as a description, but the tool description adds a concrete meaning: 'handle is the creator's page handle, e.g. CachyOS for patreon.com/CachyOS.' This is a real value-add for a single parameter, though the schema already covers most syntax.

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

Purpose5/5

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

The description open with 'Get a creator's public Patreon membership tiers' which is a specific verb-plus-resource statement, and the following sentence makes the scope exact by adding that it returns published tiers + published benefits and excludes member-only entitlements, capacity, and counts. It clearly differentiates from sibling tools like patreon_creator and patreon_explore.

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?

The description clearly implies usage context: it is for public tier data and explicitly says what is NOT included (member-only entitlements, capacity, counts), so an agent can decide when not to use it. It stops short of naming alternatives or saying 'use X instead,' so it doesn't receive a 5.

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

Deploy Server

Other Tools