Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

social_search

Read-only

Live full-text search of a source. platform="reddit": params query, subreddit? (restrict), sort? (relevance/hot/new/top/comments), time?, limit≤20. platform="hackernews": params query, sort? (relevance/new), tags? (story/ask_hn/show_hn), minPoints?, author?, since? (unix), limit≤20. 1 credit · read-only. Reddit results come via RSS (score/comments may be 0). Long bodies are truncated; fetch a single post for the full text. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoreddit: relevance|hot|new|top|comments; hackernews: relevance|new
tagsNo(hackernews) story|ask_hn|show_hn
timeNo(reddit) hour|day|week|month|year|all
limitNoMax results, 1-20 (default 20)
queryYesSearch query
sinceNo(hackernews) only items after this unix ts
authorNo(hackernews) author username
platformYesWhich source to read live: "reddit" or "hackernews".
minPointsNo(hackernews) minimum points
subredditNo(reddit) restrict to this subreddit

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint, it discloses 1-credit cost, read-only nature, RSS-caused score/comments anomalies, body truncation, and account prerequisite. These are valuable behavioral disclosures that annotations do not cover.

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?

Dense and well-organized: purpose, per-platform parameters, caveats, and prerequisite are clearly sequenced. Each sentence conveys useful information, though the length is somewhat high.

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?

Covers both platforms, parameter constraints, credit cost, known limitations, and account requirement. Missing response format details, but with no output schema and high schema coverage, it is reasonably complete for a complex 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%, so the description mainly restates parameter details with platform-specific grouping. It adds minor clarifications like limit≤20 and unix timestamp for since, but does not significantly enrich the schema definitions.

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 'Live full-text search of a source' and specifies reddit and hackernews platforms, clearly distinguishing from siblings like search_dataset and social_get_post. The verb 'search' and resource scope are specific and unambiguous.

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?

Provides platform-specific parameter breakdowns and explicitly notes limitations (RSS scores may be 0, long bodies truncated), which indirectly points to social_get_post for full text. However, it does not explicitly name alternative tools or state when not to use this tool.

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