Skip to main content
Glama

Coline

Update an issue

update_upstream_issue
DestructiveIdempotent

Changes an Upstream issue: its title, description, labels or assignees, or closes or reopens it. Labels and assignees replace the current ones.

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>",
      "repository": "<repository>",
      "number": "<number>"
    },
    "name": "update_upstream_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
stateNo
titleNo
labelsNoLabel names that exist in the repository.
numberYes
assigneesNoHandles of people who can be assigned.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.
stateReasonNoWhy it closed or reopened.

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
stateYes
titleYes
authorYes
labelsYes
numberYes
commentsYes
assigneesYes
updatedAtYes
resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is lower, and the description still adds real value by explaining that labels and assignees REPLACE the existing sets rather than merging. It does not cover permissions, error behavior for unknown labels, or partial-update semantics, which keeps it below a 5.

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?

Two short sentences, both front-loaded with the resource and the operation scope; the replace-semantics warning is placed immediately after the field list where it is most useful. No redundant restatement of the title or name.

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 an output schema present, return values need no explanation, and the schema documents the 3 required identifiers plus enum values. The description covers the mutation surface and its destructive array semantics; only edge behavior such as invalid label handling or the stateReason enum's purpose is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 56%, so the description has to compensate, and it does: it maps 'description' to body, and states the replace-not-merge behavior for labels and assignees, which the schema does not say. It is silent on stateReason, number, workspace and repository, though the latter three carry their own schema descriptions.

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?

States a specific verb ('Changes') and resource ('an Upstream issue') and enumerates the exact fields it touches (title, description, labels, assignees, open/closed state). That is enough to separate it from get_upstream_issue, list_upstream_issues and create_upstream_issue, though it never names those siblings explicitly.

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?

Usage is only implied: the field list tells the agent this is for modifying an existing issue, and the omission of comments implicitly points to comment_on_upstream_issue. There is no explicit when-to-use/when-not statement and no pointer to an alternative for commenting or creating.

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