Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

list_keywords

Retrieve the social-listening keywords your workspace tracks, with IDs, roles, platforms, aliases, and active status, to manage brand, competitor, and topic monitoring.

Instructions

List the social-listening keywords this workspace tracks — id, keyword, role (brand/competitor/topic), platforms, aliases, active state. Mentions for them arrive via list_mentions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the returned field set and workspace scope, which is valuable given there is no output schema. It omits ordering, pagination/limit behavior, and whether deactivated keywords appear — relevant for a listing tool that could return a large set.

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 short sentences, both earning their place: the first defines the resource and its fields, the second redirects to the sibling for the downstream data. Front-loaded and free of filler.

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 zero-parameter read tool with no output schema, summarizing the returned fields is the key gap-filler and it is done well. Only minor omissions remain (ordering, pagination, treatment of inactive keywords) before it would be fully self-sufficient.

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 input schema is an empty object, so there are no parameters whose semantics need clarifying; the baseline of 4 applies. Nothing in the description is needed to disambiguate arguments, and it correctly implies the call takes no filters.

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?

States a specific verb and resource ("List the social-listening keywords this workspace tracks") and enumerates what each record contains (id, keyword, role, platforms, aliases, active state). The workspace scoping and the role vocabulary (brand/competitor/topic) make it clearly distinct from sibling readers like list_mentions or list_accounts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the closing sentence routes the agent to list_mentions for the actual mentions, which hints that this tool is the entry point for discovering keyword ids. There is no explicit when-to-use/when-not statement, no mention of how it pairs with add_keyword/update_keyword/delete_keyword, and no statement about whether inactive keywords are included.

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