Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

patreon_explore

Browse public Patreon creators by topic. Returns curated creator lists, including weekly popular and new creators.

Instructions

Browse public Patreon creators by topic. Returns Patreon's public curated creator shelves for one topic: Top creators, Popular this week, and New on Patreon. topic must be one of podcasts_and_shows, visual_arts, tabletop_games, video_games, music, lifestyle, writing, handicrafts, apps_and_software, social_impact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesPublic Explore topic. Allowed values: podcasts_and_shows, visual_arts, tabletop_games, video_games, music, lifestyle, writing, handicrafts, apps_and_software, social_impact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / topic / enum
      Added value: +[
+  "podcasts_and_shows",
+  "visual_arts",
+  "tabletop_games",
+  "video_games",
+  "music",
+  "lifestyle",
+  "writing",
+  "handicrafts",
+  "apps_and_software",
+  "social_impact"
+]
  2. Addedv1.16.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Returns' public curated shelves, implying a read-only operation, and mentions 'public' to signal no auth. However, it does not mention potential limitations like rate limits, pagination, or error behavior, and does not clarify whether it modifies anything (though 'Browse' suggests not). It adds some context beyond the schema but lacks richer behavioral details expected given no annotations.

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?

The description is two sentences: the first states the main action and return type (shelves), the second enumerates the allowed topics. It is front-loaded with the core purpose and contains no fluff or redundant phrasing. Every sentence earns its place.

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?

This is a simple tool with a single enum parameter and no output schema. The description covers what it does, what it returns (three shelf types), and the valid topic values. It does not explain the structure of the returned shelves or potential errors, but those are likely self-evident for such a narrow tool. Given the low complexity, it is sufficiently complete.

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 description coverage is 100%: the schema already provides the topic enum and a description listing allowed values. The tool description repeats these values and adds the context that the topic selects one of the curated shelves, but this adds marginal value beyond the schema. Baseline of 3 is appropriate when schema covers parameters fully.

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 clearly states the action ('Browse public Patreon creators by topic') and the specific resource (curated shelves: Top creators, Popular this week, New on Patreon). This is a specific verb+resource that distinguishes it from other Patreon tools like patreon_creator or patreon_rss, even without naming them explicitly.

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 description implies usage (when you want to browse creators by topic) but does not explicitly mention when to use this tool versus alternatives like patreon_creator or patreon_creator_tiers. No exclusions or alternative tools are referenced, so guidance is implied rather than explicit.

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