Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

update_keyword

Modify a tracked keyword's settings—such as aliases, platforms, and active status—to pause or resume tracking without losing its history.

Instructions

Edit a tracked keyword — including is_active=false to pause tracking without losing history.

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": {
      "id": "<id>"
    },
    "name": "update_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKeyword id from list_keywords.
roleNo
aliasesNo
keywordNo
is_activeNofalse pauses tracking, true resumes.
platformsNo
brand_contextNo
exclude_termsNo
require_termsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It discloses exactly one trait — is_active=false pauses tracking while preserving history — and says nothing about whether unspecified fields are left unchanged, permission requirements, or reversibility of edits to keyword/aliases/platforms.

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?

A single front-loaded sentence with no padding; the pausing behavior is placed where it is most useful. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 9-parameter mutation tool with no annotations, no output schema, and 78% of parameters undocumented in both schema and description. An agent would have to guess at the meaning and effect of most of the accepted fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 22%, so the description needed to compensate for the undocumented parameters. Instead it addresses only is_active (already described in the schema) and leaves role, aliases, keyword, platforms, brand_context, exclude_terms and require_terms with no explanation anywhere.

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 states a specific verb and resource ('Edit a tracked keyword'), which unambiguously separates it from add_keyword, delete_keyword and list_keywords. It stops short of naming a sibling or stating scope conditions explicitly, so it does not reach the top tier.

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?

Use is implied by 'Edit a tracked keyword' and the hint that pausing is preferable to losing history implies the alternative (deletion). There is no explicit 'use this instead of X when Y' routing, and no prerequisites or exclusions are given.

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