What changed
The MCP tools now speak the same "keyword" language as the dashboard:
- New:
keyword_monitor_listandkeyword_monitor_create— the direct tools for the dashboard's Keyword Monitor. "Track keyword X on Reddit" now routes straight to a Reddit-wide daily search, with your quota (used/max) in every list response. - Renamed: the tools that manage tagging rules are now
tag_rule_list/tag_rule_create/tag_rule_update/tag_rule_delete, matching the dashboard's "Tagging rules" label. The oldkeyword_*names keep working as deprecated aliases — nothing breaks — but their descriptions and responses now say they've been renamed. We plan to remove the aliases after Oct 7, 2026, and only once usage shows integrations have moved. - The server now tells every connecting agent, up front, how Prowlo's three "keyword" concepts differ — Keyword Monitor, tagging rules, and the free-text
keywordsearch filter.
The story behind it
We manage Prowlo's own keyword tracking through an AI agent, and we kept watching it make the same mistake: asked to "review my tracked keywords", it confidently opened the tagging rules instead of the Keyword Monitor — twice in one week, even with a hand-written skill guiding it. The agent wasn't wrong; our tool names were. Agents are users too, so this release is a UX fix for your agent: vocabulary that matches the dashboard, and a short orientation every agent gets when it connects. After the change, a fresh agent routed the exact same request correctly on its first call.

Why it matters
When you told your agent "review my tracked keywords", the word "keyword" pointed at the wrong tool: agents landed on tagging rules (labels for posts already collected) instead of the Keyword Monitor (the Reddit-wide searches you actually meant). The vocabulary now matches what you see in the dashboard, so agents get it right on the first call.
How to use it
Nothing to reconfigure — new tool names appear the next time your agent connects. If you have scripts or skill files calling keyword_list or keyword_create, switch them to tag_rule_list / tag_rule_create when convenient.