Skip to main content
Glama

update_issue

Update a GitLab issue's attributes or state. Adjust title, description, labels, assignees, due date, weight, type, milestone, confidentiality, or discussion lock.

Instructions

Update an issue. Returns a slim confirmation by default; set full_response=true for the complete updated issue object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoThe title of the issue
labelsNoArray of label names
weightNoWeight of the issue (numeric, typically hours of work)
due_dateNoDate the issue is due (YYYY-MM-DD)
issue_iidYesThe internal ID of the project issue
issue_typeNoThe type of issue. One of issue, incident, test_case or task.
project_idYesProject ID or URL-encoded path
descriptionNoThe description of the issue
state_eventNoUpdate issue state (close/reopen)
assignee_idsNoArray of user IDs to assign issue to
confidentialNoSet the issue to be confidential
milestone_idNoMilestone ID to assign
full_responseNoIf true, return the complete updated issue object. Default returns a slim confirmation (iid, title, state, web_url, updated_at) to reduce token usage.
discussion_lockedNoFlag to lock discussions
Behavior3/5

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

The description mentions the response behavior (slim vs full) but does not disclose potential side effects like notifications, authorization requirements, or irreversibility, which are important given the 'openWorldHint' annotation.

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 sentences, each earning its place: the first states the core purpose, the second explains the response behavior. No wasted words, and the most critical information is front-loaded.

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?

Despite 14 parameters and no output schema, the description does not explain the 'slim confirmation' fields, the effect of optional parameters, or the behavior of enum parameters like 'state_event'. The openWorldHint adds to the need for more context.

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?

With 100% schema coverage, the schema already documents all parameters effectively. The description only adds value for the 'full_response' parameter, which is a minor addition. Baseline 3 is appropriate.

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 verb 'Update' and resource 'an issue', and distinguishes the default vs full response behavior, which is a unique feature. The purpose is 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?

No guidance is provided on when to use this tool versus sibling tools like 'update_issue_description_patch' or 'create_issue'. The description lacks explicit context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zereight/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server