Skip to main content
Glama
saidsef

GitHub PR Issue Analyser

by saidsef
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

update_issue

Idempotent

Update an existing GitHub issue by changing its title, body, state, or labels. Only the supplied fields are modified, leaving all other issue details unchanged.

Instructions

Updates an existing issue. Only the fields supplied are sent, the rest keep their current values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoReplacement body in Markdown. Omit to leave the current body alone
stateNoOmit to leave the issue in whichever state it is already in
titleNoReplacement title. Omit to leave the current title alone
labelsNoReplacement label set. Omit to keep the current labels, pass [] to strip them all
repo_nameYes
repo_ownerYes
issue_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
stateYes
titleYes
authorYes
labelsYes
numberYes
html_urlYes
assigneesYes
milestoneYes
created_atYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv31.0.4
    • addedOutput schema / properties / assignees
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "number",
-  "title",
-  "body",
-  "state",
-  "author",
-  "labels",
-  "milestone",
-  "html_url",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "number",
+  "title",
+  "body",
+  "state",
+  "author",
+  "labels",
+  "assignees",
+  "milestone",
+  "html_url",
+  "created_at",
+  "updated_at"
+]
  2. Changed2 schema fields changedv29.2.0
    • addedOutput schema / properties / milestone
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "number",
-  "title",
-  "body",
-  "state",
-  "author",
-  "labels",
-  "html_url",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "number",
+  "title",
+  "body",
+  "state",
+  "author",
+  "labels",
+  "milestone",
+  "html_url",
+  "created_at",
+  "updated_at"
+]
  3. Changed19 schema fields changedv29.0.0
    • addedInput schema / properties / body / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / body / default
      Added value: +null
    • addedInput schema / properties / body / description
      Added value: +"Replacement body in Markdown. Omit to leave the current body alone"
    • removedInput schema / properties / body / type
      Removed value: -"string"
    • addedInput schema / properties / labels / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / labels / default
      Previous value: -[]New value: +null
    • addedInput schema / properties / labels / description
      Added value: +"Replacement label set. Omit to keep the current labels, pass [] to strip them all"
    • removedInput schema / properties / labels / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / labels / type
      Removed value: -"array"
    • addedInput schema / properties / state / anyOf
      Added value: +[
+  {
+    "enum": [
+      "open",
+      "closed"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / state / default
      Previous value: -"open"New value: +null
    • addedInput schema / properties / state / description
      Added value: +"Omit to leave the issue in whichever state it is already in"
    • removedInput schema / properties / state / enum
      Removed value: -[
-  "open",
-  "closed"
-]
    • removedInput schema / properties / state / type
      Removed value: -"string"
    • addedInput schema / properties / title / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / title / default
      Added value: +null
    • addedInput schema / properties / title / description
      Added value: +"Replacement title. Omit to leave the current title alone"
    • removedInput schema / properties / title / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
-  "repo_owner",
-  "repo_name",
-  "issue_number",
-  "title",
-  "body"
-]New value: +[
+  "repo_owner",
+  "repo_name",
+  "issue_number"
+]
  4. Changed7 schema fields changedv19.2.0
    • addedOutput schema / properties / author
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / html_url
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / id
      Removed value: -{
-  "type": "integer"
-}
    • removedOutput schema / properties / labels / items / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / labels / items / type
      Previous value: -"object"New value: +"string"
    • removedOutput schema / properties / user
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "number",
-  "title",
-  "body",
-  "state",
-  "user",
-  "created_at",
-  "updated_at",
-  "labels"
-]New value: +[
+  "number",
+  "title",
+  "body",
+  "state",
+  "author",
+  "labels",
+  "html_url",
+  "created_at",
+  "updated_at"
+]
  5. Addedv14.0.3
  6. Removedv14.0.0
  7. Addedv11.0.1
  8. Removedv10.0.4
  9. Changed21 schema fields changedv10.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / body / title
      Removed value: -"Body"
    • removedInput schema / properties / issue_number / title
      Removed value: -"Issue Number"
    • removedInput schema / properties / labels / title
      Removed value: -"Labels"
    • removedInput schema / properties / repo_name / title
      Removed value: -"Repo Name"
    • removedInput schema / properties / repo_owner / title
      Removed value: -"Repo Owner"
    • removedInput schema / properties / state / title
      Removed value: -"State"
    • removedInput schema / properties / title / title
      Removed value: -"Title"
    • removedInput schema / title
      Removed value: -"update_issueArguments"
    • addedOutput schema / properties / body
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / created_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / id
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / labels
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / number
      Added value: +{
+  "type": "integer"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Result",
-  "type": "object"
-}
    • addedOutput schema / properties / state
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / title
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / updated_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / user
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "id",
+  "number",
+  "title",
+  "body",
+  "state",
+  "user",
+  "created_at",
+  "updated_at",
+  "labels"
+]
    • removedOutput schema / title
      Removed value: -"update_issueOutput"
  10. Addedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already mark this as non-read-only, idempotent, and non-destructive. The description adds meaningful behavioral context: only supplied fields are sent and the rest keep their current values, which is essential for predicting edit behavior. This goes beyond what the annotations alone convey, though it does not describe every possible side effect.

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 two concise sentences with no filler. The core purpose is front-loaded, and the partial-update behavior is stated immediately after, making it easy to parse. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, annotations cover safety traits, and the input schema documents each editable field, this description is complete for the tool's complexity. The partial-update semantics are the main behavioral nuance an agent needs to know, and they are explicitly provided.

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?

The input schema already documents the optional fields body, state, title, and labels with explicit 'omit to leave' descriptions. The description reinforces this with a single general rule that applies to all parameters, which is valuable. Required parameters are self-explanatory, and the 57% schema coverage is partially offset by the clear parameter names and the partial-update statement.

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 states a specific verb and resource: 'Updates an existing issue.' This clearly differentiates from create_issue and update_pr siblings by identifying both the action and the object. The second sentence adds the key partial-update scope, making the tool's purpose precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly establishes that this tool is for modifying an existing issue, which implies it should not be used to create new issues. It does not explicitly name alternatives such as create_issue, but the context is clear enough for an agent to select it correctly. No exclusions or warning conditions are described, so it falls short of a 5.

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/saidsef/mcp-github-pr-issue-analyser'

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