Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

add_keyword

Start tracking a social-listening keyword to monitor brand, competitor, or topic mentions. Results arrive on the listening pipeline’s cadence; poll list_mentions to retrieve them.

Instructions

Start tracking a social-listening keyword. Per-plan keyword caps apply (Professional 5, Enterprise 15). Mentions are fetched on the listening pipeline's own cadence — there is no fetch-now; poll list_mentions for results.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "add_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNobrand (default) vs competitor drives the Share of Voice report; topic is excluded from it.
aliasesNoAlternate spellings (max 3). Each alias costs extra search quota.
keywordYesThe keyword to track (≤100 characters).
platformsNoSources to search, e.g. ["reddit","bluesky","youtube","hackernews"]. Omit for the default set.
brand_contextNoShort description of the brand, used by the AI relevancy scorer.
exclude_termsNoSkip mentions containing any of these.
require_termsNoOnly keep mentions containing at least one of these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers meaningful behavior: per-plan keyword caps (Professional 5, Enterprise 15) and the asynchronous nature of the listening pipeline with no fetch-now. It does not cover what happens when a cap is hit or whether creation is reversible, but the async and quota context is well beyond what structured fields provide.

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?

Two sentences, both front-loaded with the most decision-relevant facts: what the tool does, then the cap and async constraints. No filler or restatement of the title.

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 7-parameter creation tool with full schema coverage and no output schema, the description supplies the essential missing context: quota caps and the fact that results arrive asynchronously via list_mentions. Only failure modes at the cap boundary are left unstated.

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%, so every parameter including role, aliases, platforms, and term filters is already documented in the schema. The description adds no parameter-specific meaning beyond the plan cap framing, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Start tracking a social-listening keyword,' which makes clear this creates a tracked keyword rather than listing or updating one. It is distinguishable from list_keywords and update_keyword by implication, though no sibling is named for contrast.

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?

It gives a clear context for use (initiating tracking) and explicitly redirects the agent to list_mentions for retrieving results, which is the key alternative an agent would otherwise confuse with this tool. It stops short of stating when to use update_keyword or delete_keyword instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.