Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

update_issue

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

Instructions

Update an existing issue in a GitHub repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes
issue_numberYes
titleNo
bodyNo
assigneesNo
milestoneNo
labelsNo
stateNo

Implementation Reference

  • MCP tool handler for 'update_issue': parses input schema, extracts parameters, calls the updateIssue helper, and returns the result as JSON.
    case "update_issue": {
      const args = issues.UpdateIssueOptionsSchema.parse(request.params.arguments);
      const { owner, repo, issue_number, ...options } = args;
      const result = await issues.updateIssue(owner, repo, issue_number, options);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • index.ts:128-132 (registration)
    Registration of the 'update_issue' tool in the MCP server's tool list, including name, description, and input schema.
    {
      name: "update_issue",
      description: "Update an existing issue in a GitHub repository",
      inputSchema: zodToJsonSchema(issues.UpdateIssueOptionsSchema)
    },
  • Zod schema defining the input structure for the 'update_issue' tool, including owner, repo, issue_number, and optional update fields.
    export const UpdateIssueOptionsSchema = z.object({
      owner: z.string(),
      repo: z.string(),
      issue_number: z.number(),
      title: z.string().optional(),
      body: z.string().optional(),
      assignees: z.array(z.string()).optional(),
      milestone: z.number().optional(),
      labels: z.array(z.string()).optional(),
      state: z.enum(["open", "closed"]).optional(),
    });
  • Helper function that executes the GitHub API PATCH request to update the specified issue with provided options.
    export async function updateIssue(
      owner: string,
      repo: string,
      issue_number: number,
      options: Omit<z.infer<typeof UpdateIssueOptionsSchema>, "owner" | "repo" | "issue_number">
    ) {
      return githubRequest(
        `https://api.github.com/repos/${owner}/${repo}/issues/${issue_number}`,
        {
          method: "PATCH",
          body: options,
        }
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Update an existing issue' implies a mutation operation, but it doesn't specify what happens with partial updates, whether changes are reversible, authentication requirements, rate limits, or error conditions. For a 9-parameter mutation tool, this leaves significant gaps in understanding its behavior.

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 states the core purpose without unnecessary words. It's appropriately front-loaded with the essential information, though this brevity comes at the cost of completeness for such a complex tool.

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 9 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely inadequate. It provides only the basic purpose without addressing parameter meanings, behavioral characteristics, usage context, or return values. The agent would struggle to use this tool correctly without additional documentation.

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

Parameters2/5

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

With 0% schema description coverage and 9 parameters (only 3 required), the description provides no information about any parameters. It doesn't mention that 'owner', 'repo', and 'issue_number' are required identifiers, nor does it explain the purpose of optional fields like 'title', 'body', 'assignees', etc. The description fails to compensate for the complete lack of schema documentation.

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 ('existing issue in a GitHub repository'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar siblings like 'create_issue' or 'get_issue' beyond the basic verb difference, missing an opportunity to clarify scope boundaries.

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. With siblings like 'create_issue' for new issues and 'get_issue' for reading, the agent must infer usage from the verb alone. There's no mention of prerequisites, permissions needed, or typical scenarios for updating versus creating issues.

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/PhialsBasement/mcp-github-server-plus'

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