zenhub-mcp

zenhub_create_epic

Create a new epic in a specified repository, optionally adding existing issues as children to organize work.

Instructions

Create a new epic in ZenHub. Optionally, you can also specify existing issue IDs that should be added as children of the new epic.

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": {
      "title": "<title>",
      "repository_id": "<repository_id>"
    },
    "name": "zenhub_create_epic"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Epic title
`repository_id`	Yes	Repository ID
`body`	No	Epic description
`epic_child_ids`	No	Array of issue IDs to add as children of the newly created epic

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 7, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose side effects, permissions, rate limits, or error scenarios for this mutation operation.

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 concise sentences that immediately state the primary action and optional feature, with no unnecessary information.

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?

Given high schema coverage and no output schema, the description effectively communicates the core functionality but lacks details on return values or behavioral context.

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 the description adds minimal value beyond stating optional child addition, which is already clear in the schema.

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 tool creates a new epic in ZenHub with an optional feature to add children, distinguishing it from the sibling tool 'zenhub_add_subissues_to_epic' which only adds children to an existing epic.

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?

The mention of optionally adding children implies when to use this tool versus 'zenhub_add_subissues_to_epic', but lacks explicit guidance on when not to use or prerequisites.

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

Deploy Server