zenhub-mcp

zenhub_create_workspace

Create a new ZenHub workspace to organize projects by specifying name, organization, repository IDs, and optional default repository.

Instructions

Create a new workspace in ZenHub

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": {
      "name": "<name>",
      "organization_id": "<organization_id>",
      "repository_ids": "<repository_ids>"
    },
    "name": "zenhub_create_workspace"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Workspace name
`description`	No	Workspace description
`organization_id`	Yes	ZenHub organization ID
`repository_ids`	Yes	GitHub repository IDs
`default_repository_id`	No	Default repository ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so the description carries full burden. It only states the creation action without disclosing behavioral traits (e.g., idempotency, duplicate handling, auth requirements, or response).

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 single sentence is concise and front-loaded. However, it could incorporate more useful details without sacrificing brevity.

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

Completeness2/5

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

With 5 parameters (3 required) and no output schema, the description is too brief. It omits return value, error handling, and post-creation state, making it incomplete for an agent to fully understand the tool.

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 covers all 5 params with descriptions (100% coverage). Description adds no extra meaning beyond the schema, so baseline of 3 is appropriate.

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?

The description clearly states the action ('Create') and the resource ('a new workspace in ZenHub'), effectively distinguishing it from retrieval ('get') and modification ('add') sibling tools.

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 guidance on when to use this tool versus alternatives, such as when to create a workspace vs. retrieve or update one. Prerequisites or side effects are not mentioned.

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

Deploy Server