Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

alert_create

Create an Alert. It fires when newly-ingested records match query. REQUIRED: query.any must have at least one mention term (brand/product/domain) — an alert with no mentions would match every record and is rejected. Per-match by default (one notification per new match, batched); provide threshold for volume/spike firing. Delivers to Slack and/or the given webhooks. Not metered. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable alert name
queryYesRecord match filter (same shape as search_dataset / list_records filters)
statusNoInitial status: "active" (default) or "paused"
thresholdNoOmit for per-match firing; provide for volume/spike firing
destinationYesAt least one of slack=true or a non-empty webhookIds is required

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses critical behavior: alerts fire only on newly-ingested records, are rejected if query.any lacks mention terms, batch notifications, and are not metered. It also surfaces the free-account requirement and signup link behavior. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with 'Create an Alert.' Each sentence adds meaningful behavior or constraints; there is no filler or redundancy.

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?

For a 5-parameter nested-object tool with no output schema, the description covers behavior, constraints, firing modes, delivery, metering, and account prerequisite. It does not describe the return value, but the absence of an output schema and rich schema descriptions partially mitigate that gap.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds key semantics not in schema: the requirement that query.any contain at least one mention term and the distinction between per-match and threshold firing. This lifts it to 4.

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?

Description opens with 'Create an Alert' – a clear verb+object. It then states the firing condition ('fires when newly-ingested records match `query`'), distinguishing from sibling alert_update/delete/list operations. The purpose is 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?

The description gives actionable usage constraints: requires at least one mention term in query.any, per-match vs threshold firing, and delivery targets. It also notes account prerequisite. It does not explicitly contrast with sibling tools (e.g., alert_update), though the create action is self-evident.

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