Skip to main content
Glama

update_issue

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

Instructions

Update an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or URL-encoded path
issue_iidYesThe internal ID of the project issue
titleNoThe title of the issue
descriptionNoThe description of the issue
assignee_idsNoArray of user IDs to assign issue to
confidentialNoSet the issue to be confidential
discussion_lockedNoFlag to lock discussions
due_dateNoDate the issue is due (YYYY-MM-DD)
labelsNoArray of label names
milestone_idNoMilestone ID to assign
state_eventNoUpdate issue state (close/reopen)
weightNoWeight of the issue (numeric, typically hours of work)
issue_typeNoThe type of issue. One of issue, incident, test_case or task.
Behavior2/5

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

Description does not disclose behavioral traits beyond annotations; openWorldHint is present but description adds no clarity on side effects, idempotency, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (one sentence, three words) but at the cost of informativeness; it is front-loaded but lacks substance.

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?

For a tool with 13 parameters and no output schema, the description fails to explain update semantics (e.g., partial vs full replacement), return values, or required 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?

Schema coverage is 100% with detailed descriptions; the tool description adds no extra meaning beyond the schema, so baseline 3 applies.

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

Purpose3/5

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

Description 'Update an issue' is a generic verb+resource but lacks specificity; it does not distinguish from sibling tools like update_issue_note or update_issue_description_patch.

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 vs alternatives; no exclusions or context provided. Agent cannot determine when to choose this tool over others.

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