Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

catalog_get_subreddit

Read-onlyIdempotent

One subreddit's card from Prowlo's tracked catalog — NOT a live Reddit call. view="stats" (default): subscribers, posts/day, comments/post, postsPerDay is sampled from the subreddit's own newest-100 /new feed (postsPerDaySpanHours = the real span those posts cover; postsPerDaySampleSize; null = not sampled in the last 14 days or fewer than 10 posts), plus activeUsers (online now at the last snapshot), title, subredditType, createdUtc (ISO), lastPostAt (ISO, newest sampled post), distinctPosterRatio (unique posters / sampled posts, 0..1) and sampleSize, growth7d + growth30d (null = not enough tracking history for that window, NOT zero growth), promoTolerance, trackingSince, plus a 5-each preview of similarByContent/similarByAudience. Set includeSeries=true only if you need the raw daily snapshot series (up to 90 points) — the growth fields already summarize it. view="similar": deeper neighbor lists only, up to limit each (similarByAudience empty = author overlap not computed yet for this sub — normal, not an error). "Not tracked" does NOT mean unwatchable — watcher_create accepts any subreddit. Free, NOT metered. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSubreddit name, with or without r/ prefix
viewNo"stats": full stat card + a 5-each similar preview. "similar": deeper similar-community lists only.stats
limitNo(view="similar" only) max neighbors per list; ignored for view="stats" (preview fixed at 5 each)
includeSeriesNo(view="stats" only) include the daily snapshot series

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses sampling behavior from the newest-100 /new feed, null semantics for growth/postsPerDay, 'similarByAudience empty = normal', free/not metered status, and account requirements. There is no contradiction with annotations.

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?

Front-loaded with the core 'tracked catalog, not live' distinction, and the long format earns its place through dense behavioral caveats. It could be tightened with clearer separation between views, but it remains logically organized.

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

Completeness5/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 fully compensates by enumerating fields, explaining both views, describing preview behavior, null signals, series limits, and account requirements. An agent has enough detail to call this tool correctly and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds substantial meaning beyond the schema: it explains what each stat represents, the sampling source, null meanings, how growth fields summarize the series, that limit is ignored for stats, and that includeSeries can return up to 90 raw points.

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 states a specific verb and resource: getting one subreddit's card from Prowlo's tracked catalog. It also explicitly says 'NOT a live Reddit call' and distinguishes the 'stats' and 'similar' views, so an agent can separate it from catalog_search_subreddits, catalog_top_subreddits, and live Reddit tools.

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 gives clear context on when to request the daily series, when to use view='similar', and notes that 'Not tracked' still permits watcher_create. It doesn't explicitly name an alternative for live Reddit data, but the strong 'NOT a live Reddit call' warning and sibling names give enough directional guidance.

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

All Prowlo — Reddit & X for AI agents toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tool pairs have overlapping purposes: keyword_* and tag_rule_* are duplicates, keyword_monitor_create is a shortcut for a subset of watcher_create, and alert_list vs get_alerts have confusingly similar names. Even though descriptions are detailed, the redundancy and naming overlap make it easy to pick the wrong tool.

Naming Consistency2/5

The set mixes object-verb names (alert_create, watcher_create) with verb-object names (get_account, list_records) and prefix-based categories (social_*). The deprecated keyword_* tools are renamed tag_rule_*, and keyword_monitor_create doesn't follow the watcher_* pattern, creating an inconsistent naming scheme.

Tool Count2/5

At 42 tools, the surface is far above the typical well-scoped range, with 5 deprecated tools and redundant paths like keyword_monitor_create vs watcher_create inflating the count. A leaner set focusing on core operations would be more manageable.

Completeness3/5

The Reddit/HN monitoring and alerting side is well covered with CRUD for watchers, tag rules, alerts, and trends plus dataset and social reads. However, the server advertises X support but has no X tools, and there's no way to post comments or manage integrations beyond viewing account info, leaving notable gaps.

Resources