Skip to main content
Glama

update_issue

Modify existing GitLab project issues by updating titles, descriptions, states, labels, assignees, or milestones to track progress and manage tasks.

Instructions

Update an existing issue in a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or URL-encoded path
issue_iidYesIssue internal ID
titleNoNew issue title
descriptionNoNew issue description
state_eventNoChange issue state
labelsNoArray of label names
assignee_idsNoArray of user IDs to assign
milestone_idNoMilestone ID to assign

Implementation Reference

  • Implementation of the updateIssue API handler, which performs a PUT request to the GitLab API to update an issue's details.
    export async function updateIssue(
      projectId: string,
      issueIid: number,
      options: {
        title?: string;
        description?: string;
        state_event?: "close" | "reopen";
        labels?: string[];
        assignee_ids?: number[];
        milestone_id?: number;
      }
    ): Promise<GitLabIssue> {
      if (!projectId?.trim()) {
        throw new Error("Project ID is required");
      }
      if (!issueIid || issueIid < 1) {
        throw new Error("Valid issue IID is required");
      }
    
      const endpoint = `/projects/${encodeProjectId(projectId)}/issues/${issueIid}`;
    
      const issue = await gitlabPut<GitLabIssue>(endpoint, {
        ...options,
        labels: options.labels?.join(",")
      });
    
      return GitLabIssueSchema.parse(issue);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states this is an update operation but doesn't cover permissions required, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It lacks critical context such as authentication requirements, side effects, error handling, and response format. The high parameter count and mutation nature demand more comprehensive guidance than provided.

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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain parameter interactions or provide examples). This meets the baseline for high schema coverage but doesn't enhance understanding.

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?

The description clearly states the action ('Update') and resource ('an existing issue in a GitLab project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'update_merge_request' or 'update_milestone' beyond the resource type, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing issue), when not to use it, or how it differs from sibling tools like 'create_issue' or 'add_issue_comment' for issue modifications.

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/TheRealChrisThomas/gitlab-mcp-server'

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