Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create issue

gitea_create_issue

Create a new issue in a Gitea repository with optional body, labels, assignees, and milestone to track bugs or tasks from your AI assistant.

Instructions

[UNIFIED] Create a new issue in a Gitea repository with optional labels, assignees, and milestone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "owner": "<owner>",
      "repo": "<repo>",
      "title": "<title>"
    },
    "name": "gitea_create_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
repoYes
siteYes
ownerYes
titleYes
closedNo
labelsNo
assigneeNo
assigneesNo
milestoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds nothing beyond that — no note about required permissions, whether duplicate titles are rejected, or that creating an issue notifies watchers. For a write tool with 10 parameters it does the minimum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler beyond the meaningless "[UNIFIED]" tag. Nothing is redundant, though the compactness comes at the cost of missing information rather than being efficiently complete.

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?

Ten parameters with no schema descriptions and no output schema means the description is the only documentation an agent has, and it covers a fraction of the surface. Important behaviors (label string format, assignee vs assignees, setting closed on creation) are left entirely to guesswork.

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 0%, so the description carries the full burden, yet it names only labels, assignees, and milestone — three of ten parameters. It does not explain the difference between the singular "assignee" and plural "assignees" fields, the format expected for labels, or what "closed" does at creation time.

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?

States a specific verb and resource ("Create a new issue in a Gitea repository") plus the optional enrichment fields, which is enough to distinguish it from close/update/comment siblings. The opaque "[UNIFIED]" prefix adds no meaning but does not obscure the purpose.

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?

No guidance on when to use this versus gitea_update_issue (for existing issues) or gitea_create_issue_comment (for adding discussion to an existing issue). The usage context is only implied by the name; there are no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools