Skip to main content
Glama

Prowlo — Reddit & X for AI agents

by com.prowlo

keyword_create

[DEPRECATED — renamed tag_rule_create. Will be removed after 2026-10-07.] Create TAGGING RULES (the dashboard's 'Tagging rules') — org-wide labels for posts your Watchers already ingest. This does NOT search Reddit: to add a Keyword Monitor entry that searches all of Reddit daily, use keyword_monitor_create instead. Each rule tags records across all your Watchers where the title or body mentions its term as a whole word — "f5bot" matches "f5bot." but not "f5bots". All languages are tagged by default; if the term is also an ordinary word in another language (the Swedish word "syften" means "purposes") and you only care about English posts, pass languageMode: "non-other" to skip records confidently detected as non-English. Pass one term as keyword or several at once as keywords. If you have no Watchers yet, create one first (with at least one subreddit) and then add rules. 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
keywordNoA single term or phrase to tag (2-100 characters)
keywordsNoSeveral terms to add in one call (2-100 characters each)
descriptionNoWhat this term refers to, e.g. "Syften is a Reddit monitoring SaaS, a competitor". Strongly recommended: matches are verified against this to weed out coincidental hits (the word "syften" also means "purposes" in Swedish). Applies to every term in this call, so pass terms with different meanings separately.
languageModeNoLanguage policy, applied to every term in this call. "any" (default) tags matches in every language. "non-other" skips records confidently detected as non-English — use it when the term is also a common word in another language; posts too short to detect a language are still tagged either way.

TDQS

A4.7/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 several key behaviors: whole-word matching, language tagging defaults, changes taking effect on the next processing cycle, and non-retroactive updates to existing scores/matches. These go well beyond what annotations convey and set correct expectations for a mutation tool.

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 long but well-structured and front-loaded with critical information (deprecation, purpose, key distinctions). Every sentence adds value, covering matching, language modes, prerequisites, timing, and retroactivity. It could be tightened but doesn't contain fluff.

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?

The description is highly complete: it covers the deprecation, prerequisites (Watchers, account), behavior, parameter usage, and limitations (no retroactive updates). It does not state the return value, but given the absence of an output schema and the tool's create nature, the description still provides sufficient contextual completeness for correct use.

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?

Although the schema already documents all parameters at 100% coverage, the description adds practical meaning: clarifies the single vs. multiple term usage ('keyword' vs 'keywords'), explains the 'description' field's role in verifying matches, and gives a concrete languageMode example with the Swedish word 'syften'. This elevates the baseline from 3 due to added context.

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 states the tool creates TAGGING RULES (org-wide labels for posts already ingested by Watchers), and explicitly distinguishes itself from keyword_monitor_create by noting it does NOT search Reddit. It also flags the deprecation and rename to tag_rule_create, providing strong differentiation 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?

The description provides explicit usage guidance: use keyword_monitor_create instead when searching Reddit, create Watchers first if none exist, and pass languageMode 'non-other' for terms with foreign-language meanings. It also mentions the deprecation and rename, giving clear direction to use tag_rule_create moving forward.

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