zenhub-mcp

zenhub_create_milestone

Create a milestone in a ZenHub repository by specifying its title, optional description, start date, and due date.

Instructions

Create a milestone

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_milestone"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Milestone title
`repository_id`	Yes	Repository ID
`description`	No	Milestone description
`due_date`	No	Due date (ISO format)
`start_date`	No	Start date (ISO format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 7, 2026

TDQS

C2.3/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 but only states 'Create a milestone'. It does not disclose behavioral traits such as whether the operation is reversible, requires authentication, or what happens on duplicate titles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While very short, the description is under-specified and does not earn its place. It lacks necessary context for effective tool selection and invocation.

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?

Given no output schema and 5 parameters, the description is grossly incomplete. It fails to explain return values, side effects, or any behavioral details essential for the agent to use the tool correctly.

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%, so baseline is 3. The description adds no additional parameter meaning beyond the schema; it merely restates the tool's purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a milestone' is clear as a verb+resource but does not differentiate from other create tools like zenhub_create_epic or zenhub_create_issue. It lacks specificity about what a milestone is in the Zenhub context.

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 is provided on when to use this tool versus alternatives (e.g., zenhub_update_milestone or other creation tools). No context about prerequisites or conditions is given.

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

Deploy Server