Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

keyword_update

Idempotent

[DEPRECATED — renamed tag_rule_update. Will be removed after 2026-10-07.] Update a TAGGING RULE (dashboard: 'Tagging rules') — not a Keyword Monitor entry (those are Watchers; see watcher_update). Rename its term (pass keyword), set what it refers to (pass description), and/or pause/resume it (pass active). Renaming keeps already-tagged records on the old tag; new matches use the new term. Changes take effect on the next scheduled processing cycle. Existing opportunity scores and matches are not retroactively updated. (requires a free Prowlo account — call it to get a signup link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe current term to update (the id returned by tag_rule_list)
activeNoWhether the rule should be active (true) or paused (false)
keywordNoNew term to rename this rule to (2-100 characters)
descriptionNoWhat this term refers to, used to verify that matches are genuinely about it. Pass an empty string to clear it.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly false, idempotent true, destructive false), the description adds valuable behavioral context: renaming keeps old tags, changes take effect later, and retroactive updates do not occur. It also mentions the account requirement. 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.

Conciseness4/5

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

The description is moderately long but each sentence serves a purpose: deprecation notice, resource clarification, parameter mapping, behavioral timing, and account note. The structure front-loads the deprecation and disambiguation, making it scannable. Slightly verbose but justified.

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 the tool's complexity and lack of output schema, the description covers all necessary context: deprecation, sibling alternatives, parameter usage, timing, retroactivity, and account prerequisite. It is sufficient for an agent to select and invoke this tool correctly.

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?

The schema already provides 100% coverage with detailed descriptions for each parameter. The description adds value by grouping parameters functionally (rename, refer to, pause/resume) and clarifying optional combinations, which aids in correct usage beyond the schema's individual property 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 the tool as updating a TAGGING RULE, explicitly distinguishing it from Keyword Monitor entries. It provides the specific verb and resource, and distinguishes from sibling tools like watcher_update and tag_rule_update. The mention of the dashboard context ('Tagging rules') further reinforces purpose.

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?

The description explicitly states when to use this tool: for tagging rules, not keyword monitors. It names the alternative tool (watcher_update) and provides deprecation guidance pointing to tag_rule_update. It also notes that changes take effect on the next scheduled cycle, giving clear context on when to expect results.

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