Skip to main content
Glama
saidsef

GitHub PR Issue Analyser

by saidsef
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

create_issue

Open a new GitHub issue in a specified repository by providing owner, repo, title, body, and labels, with optional milestone for organized tracking.

Instructions

Creates a new issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
titleYes
labelsYes
milestoneNoMilestone title to file it under. Omit for none
repo_nameYes
repo_ownerYes

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. Changed3 schema fields changedv29.2.0
    • addedInput schema / properties / milestone
      Added value: +{
+  "default": "",
+  "description": "Milestone title to file it under. Omit for none",
+  "type": "string"
+}
    • 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. 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"
+]
  4. Addedv14.0.3
  5. Removedv14.0.0
  6. Addedv11.0.1
  7. Removedv10.0.4
  8. Changed19 schema fields changedv10.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / body / title
      Removed value: -"Body"
    • 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 / title / title
      Removed value: -"Title"
    • removedInput schema / title
      Removed value: -"create_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: -"create_issueOutput"
  9. Addedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false, so the description's write-operation semantics are consistent. However, the description adds no behavioral context beyond what annotations already convey—no mention of authentication needs, side effects, validation rules, or failure scenarios. The output schema exists but the description doesn't hint at what happens after creation.

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?

The description is a single, concise sentence with no redundancy. However, it is so terse that it omits essential operational context, making it underwhelming rather than efficiently informative. It is concise but at the cost of usefulness.

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?

With 6 parameters, 5 required, and no guidance about repositories, prerequisites, or alternative tools, the description is far from complete. The presence of an output schema helps but does not replace the need for context on when and how to invoke the tool correctly.

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?

Schema description coverage is only 17% (milestone lacks a description, and the other five required parameters have none). The description does not compensate by explaining parameters like repo_owner, repo_name, title, body, or labels. While parameter names are mostly self-explanatory, the description adds zero semantic value over the bare schema.

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 'Creates a new issue.' clearly states the action (create) and object (issue), and is semantically distinct from sibling tools like update_issue and create_pr. However, it does not mention the repository context or that this is for GitHub issues, which limits full differentiation from similar creation tools.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list includes update_issue, create_pr, and create_milestone, but the description provides no criteria for choosing this tool over others, nor any exclusions or prerequisites.

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