Balzac MCP Server

create_keyword

Add keywords to your workspace to automatically gather search volume, competition, and intent data for content planning.

Instructions

Add a new keyword to the workspace. Balzac will automatically fetch search volume, competition, and intent data.

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": {
      "workspace_id": "<workspace_id>",
      "name": "<name>"
    },
    "name": "create_keyword"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	Yes	Workspace UUID
`name`	Yes	Keyword text, e.g. "content marketing strategy"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It states the tool creates a keyword and fetches data automatically, which hints at a write operation and external API calls. However, it lacks details on permissions, side effects, error handling, or rate limits, leaving behavioral gaps 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 concise and front-loaded, stating the core purpose in the first sentence. The second sentence adds value by explaining automatic data fetching, avoiding redundancy. It could be slightly more structured but remains efficient with no wasted words.

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

Completeness3/5

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

Given no annotations and no output schema, the description is moderately complete for a simple creation tool. It covers the basic action and outcome but lacks details on return values, error cases, or integration with sibling tools, leaving room for improvement in contextual depth.

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 description coverage is 100%, providing clear parameter details. The description adds minimal semantics by implying 'name' is the keyword text and that data is fetched post-creation, but doesn't elaborate beyond the schema's descriptions. Baseline 3 is appropriate as the schema handles most documentation.

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 clearly states the action ('Add a new keyword') and resource ('to the workspace'), specifying it's for creation. It distinguishes from siblings like 'delete_keyword' or 'list_keywords' by focusing on addition, but doesn't explicitly contrast with similar creation tools like 'create_workspace' or 'create_briefing'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives is provided. It mentions automatic data fetching, which implies usage for keyword setup, but lacks context on prerequisites, timing, or comparisons to siblings like 'generate_suggestions' or 'generate_long_tail_keywords' for keyword-related tasks.

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