Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

get_usage

Read-onlyIdempotent

Get your daily live-read usage: today's passthrough count, your daily cap, and reset time. Live-Reddit reads (social_search, social_list_posts, social_get_post, social_get_user, social_get_user_activity, social_find_channels) count toward a daily cap, charged on success. research_run draws from the AI-credit pool (first run per org free; later runs use credits — the balance is in aiCredits). Internal-data reads (list_records, search_dataset, get_record, list_watchers, get_dataset_summary, get_crawl_activity, get_alerts, get_account), catalog reads (catalog_search_subreddits, catalog_get_subreddit, catalog_top_subreddits) and research_get are NOT metered — only rate-limited. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark readOnly/idempotent; description adds major behavioral detail beyond annotations: which operations are metered/charged, which use AI credits, which are rate-limited only, and that an account is required. 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 a one-sentence core outcome, followed by structured detail on metering categories. It is longer than typical because it enumerates many sibling tools, but the detail is relevant; still, the enumeration could be condensed into named groups.

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?

For a zero-parameter tool with no output schema, it is complete: it states the output fields, billing/metering rules, what is not metered, and the account prerequisite. An agent can invoke and interpret results without needing further context.

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?

Tool has zero parameters and 100% schema coverage (empty schema), so there is nothing for the description to add about inputs. The description instead clarifies what the response covers, satisfying the baseline for no-parameter tools.

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?

States a specific verb and resource: get daily live-read usage, with concrete returned values (passthrough count, daily cap, reset time). It clearly differs from sibling tools by focusing on usage/quota rather than data operations.

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?

Description gives clear context on when to call: to see live-read usage against cap, AI-credit balance, and signup link if no account. It doesn't explicitly list alternatives or exclusions, but no sibling serves the same metering role.

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