Skip to main content
Glama

create-issue

Create new issues in GitHub repositories to report bugs, request features, or track tasks directly through the GitHub MCP Server.

Instructions

Create a new issue in a GitHub repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
titleYesIssue title
bodyYesIssue body
labelsNoLabels to apply to the issue

Implementation Reference

  • The handler function that implements the 'create-issue' tool logic. It uses the Octokit client to create a new issue in a GitHub repository and returns the issue details or an error message.
    const createIssue = async (args: CreateIssueArgs) => {
      const { owner, repo, title, body, labels = [] } = args;
      
      try {
        const response = await octokit.rest.issues.create({
          owner,
          repo,
          title,
          body,
          labels,
        });
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  number: response.data.number,
                  title: response.data.title,
                  url: response.data.html_url,
                  created_at: response.data.created_at,
                  message: "Issue created successfully",
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        return {
          content: [
            {
              type: "text",
              text: `Error creating issue: ${errorMessage}`,
            },
          ],
        };
      }
    };
  • The schema definition for the 'create-issue' tool, including inputSchema with properties for owner, repo, title, body, and optional labels.
    "create-issue": {
      name: "create-issue",
      description: "Create a new issue in a GitHub repository",
      inputSchema: {
        type: "object",
        properties: {
          owner: {
            type: "string",
            description: "Repository owner (username or organization)",
          },
          repo: {
            type: "string",
            description: "Repository name",
          },
          title: {
            type: "string",
            description: "Issue title",
          },
          body: {
            type: "string",
            description: "Issue body",
          },
          labels: {
            type: "array",
            items: {
              type: "string"
            },
            description: "Labels to apply to the issue",
          }
        },
        required: ["owner", "repo", "title", "body"],
      },
    },
  • src/tools.ts:322-327 (registration)
    Export of toolHandlers object that maps tool names to their handler functions, including 'create-issue' to createIssue.
    export const toolHandlers = {
      "search-repos": searchRepos,
      "get-repo-info": getRepoInfo,
      "list-issues": listIssues,
      "create-issue": createIssue,
    };
  • src/handlers.ts:19-21 (registration)
    Registration of ListToolsRequestSchema handler, which exposes all tool schemas (including create-issue) via Object.values(tools).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: Object.values(tools)
    }));
  • src/handlers.ts:22-32 (registration)
    Registration of CallToolRequestSchema handler, which dispatches to the appropriate tool handler (including createIssue for 'create-issue') based on name.
        server.setRequestHandler(CallToolRequestSchema, async (request) => {
            type ToolHandlerKey = keyof typeof toolHandlers;
            const { name, arguments: params } = request.params ?? {};
            const handler = toolHandlers[name as ToolHandlerKey];
    
            if (!handler) throw new Error("tool not found");
    
            type HandlerParams = Parameters<typeof handler>;
            return handler(params as any);
        })
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, it doesn't disclose authentication requirements, rate limits, error conditions, or what happens on success (e.g., returns issue ID). For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a tool with good schema documentation and gets straight to the point.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (return values), authentication needs, error handling, or constraints. Given the complexity of creating GitHub issues, more context would be helpful.

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 description coverage is 100%, with all parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline expectation but doesn't provide extra value.

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 clearly states the action ('Create a new issue') and target resource ('in a GitHub repository'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list-issues' or 'search-repos' beyond the obvious create vs. read distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication, repository access), when not to use it, or how it differs from similar operations in sibling tools beyond the basic verb difference.

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