gh_mcp

by fvanevski

Overview Schema Related Servers Score Discussions

Python

Local

Create issue or pull request comment

gh_create_comment

Add a comment to a GitHub issue or pull request after verifying the repository and issue identity via an API call.

Instructions

Additive write: post exactly one bounded Markdown conversation comment on the specified issue or pull request after ordinary write authorization. The mutation is attempted once through the issue-comments REST endpoint, and authoritative readback of the returned immutable comment ID verifies repository and issue identity plus the requested body. It is not a formal pull-request review and cannot merge.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Markdown comment body.
`repo`	Yes	GitHub repository name without the owner prefix.
`owner`	Yes	GitHub repository owner or organization login.
`issue_number`	Yes	Issue or pull request number to comment on.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`message`	Yes
`warning`	No
`comment_id`	No
`request_id`	No
`write_completed`	Yes
`readback_completed`	Yes
`precondition_checked`	Yes
`state_matches_requested`	Yes

Schema Changelog

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

Changed21 schema fields changedv0.8.1Aug 19, 2026

addedInput schema / properties / body / description
```
Added value: +"Markdown comment body."
```
addedInput schema / properties / body / maxLength
```
Added value: +65536
```

addedInput schema / properties / issue_number / description

Added value: +"Issue or pull request number to comment on."

addedInput schema / properties / issue_number / minimum
```
Added value: +1
```

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}$"
```

changedOutput schema / description

Previous value: -"Result of creating a comment."New value: +"Authoritative result of creating an issue or pull-request comment."

addedOutput schema / properties / comment_id

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Comment Id"
+}

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: -[
-  "url",
-  "message"
-]New value: +[
+  "precondition_checked",
+  "write_completed",
+  "readback_completed",
+  "state_matches_requested",
+  "url",
+  "message"
+]

First observedv0.1.0Aug 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that this is an 'additive write' (non-destructive), attempted once through a specific endpoint, and that it readback verifies via the immutable comment ID. It also communicates the lack of merge/review capability. This adds meaningful behavioral context without contradicting the annotations.

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, well-structured paragraph that front-loads the primary purpose and uses each sentence to add value: action, mechanics, verification, and exclusion. There is no wasted text or repetition of schema annotations.

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

Completeness4/5

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

The description provides enough context for an agent to decide when and how to invoke the tool: it identifies the endpoint, notes the write authorization requirement, explains readback verification, and disambiguates from review/merge operations. It could mention expected side effects or rate limits, but given the output schema and annotations, the description is largely complete for this simple mutation tool.

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?

Schema coverage is 100%, so the baseline is 3. The description does not add parameter-specific details beyond what the schema already provides; it mentions 'body' and 'Markdown comment' but the schema already describes these. It does not compensate for any coverage gaps since there are none.

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 opens with 'Additive write' and uses a specific verb 'post' to state it creates a comment on a specified issue or pull request. It clearly defines the resource (issue/PR), the content (bounded Markdown comment), and the mechanism (issue-comments REST endpoint). It also distinguishes itself from siblings by stating 'It is not a formal pull-request review and cannot merge.'

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 gives clear context on when to use this tool (to comment on an issue or PR) and explicitly excludes the review/merge capability, guiding an agent away from using it for those purposes. It doesn't explicitly name alternative tools, but the exclusion is enough to differentiate it from related siblings like gh_comment_pr_review or gh_merge_pr.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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