Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_add_labels_to_issues

Add labels to multiple issues in your ZenHub workspace to organize and categorize them.

Instructions

Add labels to multiple 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>",
      "labels": "<labels>"
    },
    "name": "zenhub_add_labels_to_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idsYesArray of issue IDs
labelsYesArray of label names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior fully. It only states 'add labels' without specifying if labels must exist, whether labels are appended or replaced, or any side effects.

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?

Single sentence with no waste, but could be more informative while remaining concise.

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?

No annotations or output schema; description lacks essential behavioral context for a mutation tool, such as whether labels are appended or set, and error conditions.

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 descriptions cover both parameters (100% coverage), so description adds no additional meaning beyond what the schema provides. Baseline 3 applies.

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?

Description uses specific verb 'add' and resource 'labels to multiple issues', clearly distinguishing it from sibling tools like zenhub_remove_labels_from_issues and label creation 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; no mention of prerequisites or exclusion of other tools like zenhub_remove_labels_from_issues.

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