Skip to main content
Glama

Change several error issues

update_error_issues

The same change on up to 100 issues: resolve, ignore or reopen them, assign them, set their priority, or add a note to each. Answers per issue, with counts. Only works when the app allows MCP writes (Issues settings → Let MCP keys change 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>"
    },
    "name": "update_error_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
statusNo
assigneeNo
priorityNo
issue_idsYesIssue ids, from list_error_issues
resolved_in_releaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare it as a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds genuine context beyond that: the 100-item cap, the per-issue response with counts, and the write-permission toggle. It doesn't say what happens to invalid/foreign ids or whether the operation is all-or-nothing across the batch, which matters for a non-idempotent batch mutation.

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?

Three compact sentences, each earning its place: scope and fields first, return shape second, precondition last. No filler or restatement of the title.

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?

With no output schema, the 'answers per issue, with counts' sentence usefully covers the return shape, and the permission caveat covers the main failure mode. Remaining gaps are partial-failure behavior and the undocumented resolved_in_release parameter.

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 only 17% (six params), so the description carries real weight and does explain status semantics (resolve/ignore/reopen) and the assign/priority/note actions. It omits resolved_in_release entirely and never maps the plain-language verbs to the actual enum values (resolved/ignored/ongoing).

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?

States a specific verb and resource with its batch scope ('the same change on up to 100 issues') and enumerates the mutatable fields (status, assignee, priority, note). The 'several/up to 100' framing distinguishes it from the singular sibling update_error_issue without needing to open the schema.

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?

Gives a real precondition ('Only works when the app allows MCP writes… Issues settings → Let MCP keys change issues') and implies the batch use case. It doesn't explicitly say when to choose this over update_error_issue for a single id, so guidance is strong but not fully routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources