Skip to main content
Glama

Create GitHub issue

wopee_create_github_issue

Create a GitHub issue to report bugs, track test failures, or add action items from testing sessions.

Instructions

Create a new GitHub issue in the project's connected repository. Use this to report bugs found during testing, track test failures, or create action items from chat discussions. The issue will be created in the GitHub repository linked to the current project. Requires the project to have GitHub integration configured and WOPEE_PROJECT_UUID to be set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title of the GitHub issue
bodyYesThe body/description of the GitHub issue (supports Markdown)
labelsNoOptional labels to apply to the issue (e.g., ['bug', 'testing'])

Implementation Reference

  • The main handler definition for the 'wopee_create_github_issue' tool. It validates input via Zod schema, reads WOPEE_PROJECT_UUID from config, sends a GraphQL mutation (CreateGitHubIssue) via requestClient, and returns the created issue details (URL, number, title) or an error message.
    export const wopeeCreateGithubIssue = {
      name: ToolName.WOPEE_CREATE_GITHUB_ISSUE,
      config: {
        title: "Create GitHub issue",
        description:
          "Create a new GitHub issue in the project's connected repository. Use this to report bugs found during testing, track test failures, or create action items from chat discussions. The issue will be created in the GitHub repository linked to the current project. Requires the project to have GitHub integration configured and WOPEE_PROJECT_UUID to be set.",
        inputSchema: InputSchema.shape,
      },
      handler: async (input: Input) => {
        try {
          const { WOPEE_PROJECT_UUID } = getConfig();
    
          if (!WOPEE_PROJECT_UUID)
            return {
              content: [
                { type: "text" as const, text: "WOPEE_PROJECT_UUID is not set" },
              ],
            };
    
          const result = await requestClient<{
            createGitHubIssue: {
              url: string;
              number: number;
              title: string;
            } | null;
          }>(CreateGitHubIssue, {
            projectUuid: WOPEE_PROJECT_UUID,
            title: input.title,
            body: input.body,
            labels: input.labels || [],
          });
    
          if (!result?.createGitHubIssue)
            return {
              content: [
                {
                  type: "text" as const,
                  text: "Failed to create GitHub issue. Make sure the project has GitHub integration configured.",
                },
              ],
            };
    
          return {
            content: [
              {
                type: "text" as const,
                text: `GitHub issue created successfully:\n- Title: ${result.createGitHubIssue.title}\n- Number: #${result.createGitHubIssue.number}\n- URL: ${result.createGitHubIssue.url}`,
              },
            ],
          };
        } catch (error) {
          return _parseError(error);
        }
      },
    };
  • Zod input schema for the tool: requires 'title' (string) and 'body' (string with Markdown), with optional 'labels' (array of strings).
    const InputSchema = z.object({
      title: z.string().describe("The title of the GitHub issue"),
      body: z
        .string()
        .describe("The body/description of the GitHub issue (supports Markdown)"),
      labels: z
        .array(z.string())
        .optional()
        .describe(
          "Optional labels to apply to the issue (e.g., ['bug', 'testing'])",
        ),
    });
  • Enum registration of the tool name 'WOPEE_CREATE_GITHUB_ISSUE' in the ToolName enum, mapping to the string 'wopee_create_github_issue'.
    WOPEE_CREATE_GITHUB_ISSUE = "wopee_create_github_issue",
  • Import of wopeeCreateGithubIssue from its module directory.
    import { wopeeCreateGithubIssue } from "./wopee_create_github_issue/index.js";
  • Registration of wopeeCreateGithubIssue in the TOOLS array, making it available to the MCP server.
    wopeeCreateGithubIssue,
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the issue is created in the linked repository and requires configuration. However, it does not disclose whether the operation is idempotent, any side effects (e.g., notification triggers), or what happens on failure. The absence of such details leaves some behavioral ambiguity.

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?

The description is concise with four sentences, front-loaded with the main purpose. Every sentence adds value: purpose, use cases, location, prerequisites. Could be slightly more streamlined, but overall efficient.

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?

Given the lack of annotations and output schema, the description should explain what the tool returns (e.g., issue URL or number) or error conditions. It fails to do so, leaving the agent unaware of the tool's output. This gap reduces completeness.

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 schema already documents the parameters. The description adds no additional meaning beyond stating that labels are optional (already in schema) and that the body supports Markdown (also in schema). Thus, it does not exceed the baseline of 3.

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 clearly states the action (creating a GitHub issue) and the resource (project's connected repository). It lists specific use cases (report bugs, track failures, action items) and the verb 'Create' is precise. Although it does not explicitly distinguish from siblings, the sibling tools are all different actions (suite creation, analysis, etc.), so purpose 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 explicit scenarios for use: reporting bugs, tracking test failures, and creating action items from chat discussions. It also mentions prerequisites (GitHub integration configured and WOPEE_PROJECT_UUID set). However, it does not state when not to use the tool or mention alternatives, but given no alternative issue-creation tools exist among siblings, this is minor.

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/Wopee-io/wopee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server