Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

list_records

Read-onlyIdempotent

List records in your Dataset (Prowlo’s indexed posts from crawled sources). NOT a live Reddit call — free, rate-limited only. Filter by view (all/matched), subreddits, platforms, tags, keyword, any (brand-variant OR-group), include/exclude, intent, score/comments, date range, watcherId. Paginated via cursor. Note: tags / watcherId are record-level, so passing either uses the "matched" view automatically. Records whose keyword match was AI-judged coincidental are hidden by default (pass includeSuppressed:true to see them; each record carries a verification field). A filtered page can hold fewer than limit items — page until nextCursor is null. Long record bodies are trimmed to keep the page scannable — use get_record for a record’s full body. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoISO date upper bound (created on platform)
anyNoMatch if title/body contains ANY of these terms (brand monitoring → your brand + variants)
fromNoISO date lower bound (created on platform)
tagsNoRestrict to records carrying any of these rule tags
viewNo"matched" = only records that matched a Watcher ruleall
limitNoMax records to return, 1-40 (default 25); page with cursor for more
cursorNoPagination cursor from a previous response
intentNo(COMING SOON — not yet available) Filter by author intent: BUYING, SELLING, or DISCUSSING. Posts are not intent-classified yet, so this filter currently returns no matches.
excludeNoNone of these may appear in title/body
includeNoStricter: EVERY term must appear in title/body
keywordNoSingle free-text term in title/body
minScoreNoMinimum post score (platform upvotes/points)
platformsNoe.g. ["reddit","hackernews"]
watcherIdNoRestrict to records from one of your Watchers (by id)
subredditsNoRestrict to these subreddits/channels (no r/ prefix)
minCommentsNoMinimum number of comments
includeSuppressedNoInclude records whose keyword match was judged "coincidental" by AI mention verification (the term appeared but the post is not about it). Default false — such records are hidden. Every returned record carries a `verification` field (confirmed | coincidental | pending | clear) either way.

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the readOnly/idempotent hints, disclosing pagination quirks (page can hold fewer than limit), suppression of coincidental matches, the `verification` field, automatic switch to 'matched' view for tags/watcherId, and trimming of long bodies. These are important behavioral traits not in 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 dense but every sentence adds value: purpose, non-live caveat, filter summary, pagination, behavioral quirks, and full-body redirect. It is well-structured and front-loaded with the core purpose.

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?

Given 17 parameters and no output schema, the description covers key return behavior (verification field, trimming), pagination semantics, account requirement, rate limit, and relationship to get_record. This is a fully-specified context for a complex tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaningful parameter context: explains `any` as brand-variant OR-group, the side effect of tags/watcherId forcing matched view, and the includeSuppressed behavior. This goes beyond schema descriptions.

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 identifies a specific verb (List) and resource (records in your Dataset), and distinguishes itself from a live Reddit call and from get_record (which retrieves full bodies). This is a specific, non-generic purpose that differentiates from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when NOT to use it ('NOT a live Reddit call') and redirects to an alternative for a related need ('use get_record for a record’s full body'). This provides clear usage context versus siblings.

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