gh_mcp

Overview Schema Related Servers Score Discussions

Create label

gh_create_label

Create a new GitHub repository label with a specified name, color, and optional description. This action adds exactly one label without overwriting existing labels or modifying issues.

Instructions

Additive write: create exactly one new repository label after ordinary write authorization. Name, color, and description are explicitly bounded; one mutation attempt is followed by authoritative semantic readback. The operation never overwrites an existing label or retries an ambiguous create automatically, and it does not edit issues or delete labels.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	New label name.
`repo`	Yes	GitHub repository name without the owner prefix.
`color`	Yes	Six-character hexadecimal label color.
`owner`	Yes	GitHub repository owner or organization login.
`description`	No	Optional label description.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`color`	No
`message`	Yes
`warning`	No
`request_id`	No
`description`	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.

Changed25 schema fields changedv0.8.1Aug 19, 2026

addedInput schema / properties / color / description

Added value: +"Six-character hexadecimal label color."

addedInput schema / properties / color / pattern
```
Added value: +"^[0-9A-Fa-f]{6}$"
```

changedInput schema / properties / description / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 65536,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / description / description
```
Added value: +"Optional label description."
```

removedInput schema / properties / force

Removed value: -{
-  "default": false,
-  "title": "Force",
-  "type": "boolean"
-}

addedInput schema / properties / name / description
```
Added value: +"New label name."
```
addedInput schema / properties / name / maxLength
```
Added value: +100
```
addedInput schema / properties / name / minLength
```
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 label."New value: +"Authoritative outcome of one label creation attempt."

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

changedOutput schema / title

Previous value: -"LabelCreate"New value: +"LabelCreateResult"

First observedv0.1.0Aug 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that one mutation attempt is followed by authoritative semantic readback, that it never overwrites or retries ambiguous creates, and that it does not edit issues or delete labels. This adds significant behavioral context regarding auth, scope, and post-action verification.

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?

Three sentences front-load the core purpose and then concisely add critical behavioral details. Every sentence earns its place; there is no fluff or repetition of schema content.

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?

For a mutation tool, the description covers auth, non-idempotency, exact scope, post-write readback, and what it avoids. With a full schema and output schema present, the description is complete enough for an agent to select and invoke the tool correctly.

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% with each parameter described. The description adds that name, color, and description are 'explicitly bounded,' which reinforces but does not extend the schema constraints. It does not add new parameter-specific semantics beyond the schema.

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 uses a specific verb and resource ('create exactly one new repository label') and clearly distinguishes from siblings by stating it does not edit issues or delete labels. The scope is unambiguous.

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 provides clear context: it is additive, creates one label, and never overwrites an existing label, implying that editing should be done elsewhere. It also notes ordinary write authorization as a prerequisite. It does not explicitly name alternative tools, but the exclusions help an agent decide when not to use it.

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