Fetch a user's recent submissions or comments. kind=submissions|comments (default submissions). reddit via RSS (newest-first, ~20). 1 credit · read-only. (requires a free Prowlo account — call it to get a signup link)
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | submissions | |
| limit | No | ||
| platform | Yes | Which source to read live: "reddit" or "hackernews". | |
| username | Yes | Username, no u/ prefix |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses credit cost, account requirement with signup link behavior, and source details (reddit via RSS, newest-first, ~20). This adds meaningful behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is tightly packed: main purpose, kind parameter, source/ordering, cost, and account requirement are each conveyed in brief clauses. It front-loads the purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with no output schema, the description covers the core semantics, source, ordering, cost, and account prerequisite. It doesn't explicitly describe the return structure, but that is implicit in 'fetch submissions or comments'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description clarifies the kind parameter ('kind=submissions|comments (default submissions)') and hints at the limit default (~20). The schema already documents platform and username, so this complements rather than repeats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence 'Fetch a user's recent submissions or comments' clearly states the tool's function with a specific verb and resource, and the kind parameter specification distinguishes it from sibling tools like social_get_user or social_get_post.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives implied usage context (fetching recent activity for a user) but does not explicitly name alternatives or state when not to use this tool. It mentions credit cost and account requirement, which are prerequisites, but no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
