Skip to main content
Glama
fvanevski

gh_mcp

by fvanevski
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Create issue

gh_create_issue

Create a new GitHub issue in a specified repository with optional labels and assignees. Ensures a single additive mutation without editing or closing existing issues.

Instructions

Additive write: create exactly one issue in the target repository. The ordinary write gate and repository policy must allow the target. Optional labels and assignees are bounded; one mutation attempt is followed by authoritative semantic readback when stable identity is available. The tool never retries an ambiguous mutation automatically and does not edit, close, comment on, or delete an existing issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional Markdown issue body.
repoYesGitHub repository name without the owner prefix.
ownerYesGitHub repository owner or organization login.
titleYesIssue title.
labelsNoOptional labels to apply.
assigneesNoOptional GitHub user logins or the @me selector to assign.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
titleYes
numberYes
messageYes
warningNo
request_idNo
write_completedYes
readback_completedYes
precondition_checkedYes
state_matches_requestedYes

Schema Changelog

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

  1. Changed27 schema fields changedv0.8.1
    • changedInput schema / properties / assignees / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 39,
+      "minLength": 1,
+      "pattern": "^(?:@me|[A-Za-z0-9](?:[A-Za-z0-9-]{0,38}))$",
+      "type": "string"
+    },
+    "maxItems": 10,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / assignees / description
      Added value: +"Optional GitHub user logins or the @me selector to assign."
    • changedInput schema / properties / body / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 65536,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / body / description
      Added value: +"Optional Markdown issue body."
    • changedInput schema / properties / labels / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 100,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 100,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / labels / description
      Added value: +"Optional labels to apply."
    • addedInput schema / properties / owner / description
      Added value: +"GitHub repository owner or organization login."
    • addedInput schema / properties / owner / maxLength
      Added value: +39
    • addedInput schema / properties / owner / minLength
      Added value: +1
    • addedInput schema / properties / owner / pattern
      Added value: +"^[A-Za-z0-9](?:[A-Za-z0-9-]{0,38})$"
    • addedInput schema / properties / repo / description
      Added value: +"GitHub repository name without the owner prefix."
    • addedInput schema / properties / repo / maxLength
      Added value: +100
    • addedInput schema / properties / repo / minLength
      Added value: +1
    • addedInput schema / properties / repo / pattern
      Added value: +"^[A-Za-z0-9_.-]{1,100}$"
    • addedInput schema / properties / title / description
      Added value: +"Issue title."
    • addedInput schema / properties / title / maxLength
      Added value: +256
    • addedInput schema / properties / title / minLength
      Added value: +1
    • changedOutput schema / description
      Previous value: -"Result of creating an issue."New value: +"Authoritative outcome of one issue creation attempt."
    • addedOutput schema / properties / number / minimum
      Added value: +0
    • addedOutput schema / properties / precondition_checked
      Added value: +{
+  "title": "Precondition Checked",
+  "type": "boolean"
+}
    • addedOutput schema / properties / readback_completed
      Added value: +{
+  "title": "Readback Completed",
+  "type": "boolean"
+}
    • addedOutput schema / properties / request_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Request Id"
+}
    • addedOutput schema / properties / state_matches_requested
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "State Matches Requested"
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Warning"
+}
    • addedOutput schema / properties / write_completed
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Write Completed"
+}
    • changedOutput schema / required
      Previous value: -[
-  "number",
-  "title",
-  "url",
-  "message"
-]New value: +[
+  "precondition_checked",
+  "write_completed",
+  "readback_completed",
+  "state_matches_requested",
+  "number",
+  "title",
+  "url",
+  "message"
+]
    • changedOutput schema / title
      Previous value: -"IssueCreate"New value: +"IssueCreateResult"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by explaining that it performs an authoritative readback when stable identity is available and that it never retries ambiguous mutations. It also explicitly states it does not edit, close, comment, or delete existing issues, providing full transparency.

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 concise and structured, with each sentence carrying relevant information about the operation, gates, readback, retry behavior, and scope. No unnecessary fluff is present.

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?

The description provides complete context about the mutation's behavior, including the readback confirmation, retry policy, and explicit scope limitations. Given that an output schema exists, the lack of return value details is acceptable.

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 descriptions are comprehensive for all parameters, covering owner, repo, title, body, labels, and assignees with constraints. The tool description does not add further parameter-specific meaning, so it stays at the baseline given high schema coverage.

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 tool creates exactly one issue in a target repository, which is a specific verb-resource pair. It also specifies 'additive write', distinguishing it from edit or delete operations.

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 mentions the requirement of write gate and repository policy, indicating when it's allowed, but it does not explicitly contrast with alternative tools like edit or state change. However, the 'additive write' phrasing implies usage for creation, which is fairly explicit.

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/fvanevski/gh_mcp'

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