Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_reopen_issues

Reopen closed issues by specifying issue IDs, target pipeline, and position (start or end) to restore them to an active workflow.

Instructions

Reopen one or more closed issues

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": {
      "issue_ids": "<issue_ids>",
      "pipeline_id": "<pipeline_id>"
    },
    "name": "zenhub_reopen_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idsYesArray of issue IDs
pipeline_idYesPipeline ID to move issues to
positionNoPosition in pipeline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description only states the basic mutation (reopen). It lacks details on side effects, required permissions, or any potential impacts. The description is insufficient for understanding behavior beyond the action itself.

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?

The description is one sentence of five words with no filler. Every word is necessary. It is as concise as possible while conveying the purpose.

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?

The tool has three parameters and no output schema. While the schema covers parameters, the description lacks overarching context such as typical usage, error conditions, or what happens after reopening. It is too minimal for a practical scenario.

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?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not clarify the role of pipeline_id or position in the reopen context.

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 'Reopen' and the target 'closed issues', distinguishing it from 'zenhub_close_issues' which performs the opposite action. It is specific and unambiguous.

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?

The description does not provide any context for when to use this tool versus alternatives, such as prerequisites (issues must be closed) or when not to use it. No sibling differentiation is discussed.

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

Deploy Server

Other Tools