alert_delete
DestructiveIdempotent
Delete an Alert by id. Not metered. (requires a free Prowlo account — call it to get a signup link)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Alert id to delete (from alert_list) |
Prowlo — Reddit & X for AI agents
by com.prowlo
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds non-metered status and account requirement beyond what annotations provide. However, the ambiguous 'call it to get a signup link' could mislead, and no mention of effects on related resources or recovery options.
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?
Very brief and front-loaded, but the parenthetical is awkward and the fragment 'Not metered.' could be smoother. Still, every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool, annotations and schema cover the essentials. The description adds cost and prerequisite context, but the ambiguous signup link instruction leaves a gap, and no return behavior is described.
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% with a useful parameter description ('Alert id to delete (from alert_list)'). The tool description itself adds no additional parameter semantics, so baseline 3 is appropriate.
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?
Clearly states 'Delete an Alert by id' with a specific verb and resource. This distinguishes it from siblings like alert_create and alert_update.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides prerequisite context (requires a Prowlo account) and cost info (Not metered), but no guidance on when to use this vs alternatives. The confusing 'call it to get a signup link' phrase does not clarify usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.