huly-mcp-selfhost

bulk_update_issues

Destructive

Apply a single change to many issues at once, validating every update first to prevent partial or invalid edits.

Instructions

Apply one change to many issues; validates all first

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": {
      "workspace": "<workspace>",
      "identifiers": "<identifiers>"
    },
    "name": "bulk_update_issues"
  }
}

Input Schema

Name	Required	Description
`dueDate`	No	null clears
`assignee`	No	Person name; null clears
`priority`	No
`workspace`	Yes
`statusName`	No
`identifiers`	Yes	Issue ids
`componentLabel`	No	Component name; null clears
`milestoneLabel`	No	Milestone name; null clears

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, so safety is signalled. The description does add one genuinely useful behavioral fact beyond annotations — "validates all first" implies pre-flight validation before any mutation — but it never states what happens on partial failure (atomic vs per-issue), what error output looks like, or whether only one field may be set per call.

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?

Two clauses, no filler, and the bulk scope plus validation behavior are front-loaded in a single sentence. The terseness is efficient at the sentence level but leaves the definition thin overall.

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?

This is a destructive bulk mutation with 8 parameters, no output schema, and no guidance on atomicity, batch limits, or error behavior. For a tool that can modify many records at once, the one-line description does not carry enough information for confident invocation.

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 63%, with the null-clearing semantics already documented per field in the schema. The description adds no parameter detail at all — notably it does not clarify whether "one change" means exactly one of the eight mutable fields may be supplied, which is the key ambiguity for this schema.

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

Purpose4/5

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

"Apply one change to many issues" names a concrete verb (apply/update) and resource (issues) plus the bulk scope, which naturally separates it from the single-issue update_issue sibling. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "many issues" implies the bulk use case, but there is no explicit when-to-use/when-not guidance, no pointer to update_issue for single edits, and no note on prerequisites such as permissions or a maximum batch size.

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

Deploy Server