Skip to main content
Glama

Create GitHub issue

wopee_create_github_issue

Create a GitHub issue to report bugs found during testing or track test failures. Uses the project's connected repository with required title and body.

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 tool handler for 'wopee_create_github_issue'. It reads WOPEE_PROJECT_UUID from config, sends a GraphQL mutation (CreateGitHubIssue) with title, body, and optional labels to create a GitHub issue, and returns the result URL/number/title.
    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 defining the expected inputs: title (string), body (string, Markdown), and 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'])",
        ),
    });
  • The tool is imported from './wopee_create_github_issue/index.js' and registered in the TOOLS array at line 27.
    import { wopeeCreateGithubIssue } from "./wopee_create_github_issue/index.js";
    
    export const TOOLS = [
      wopeeCreateBlankSuite,
      wopeeFetchAnalysisSuites,
      wopeeFetchExecutedTestCases,
    
      wopeeDispatchAnalysis,
      wopeeDispatchAgent,
    
      wopeeFetchArtifact,
      wopeeUpdateArtifact,
      wopeeGenerateArtifact,
    
      wopeeSendChatMessage,
      wopeeReadChatHistory,
      wopeeCreateGithubIssue,
    ];
  • Enum value ToolName.WOPEE_CREATE_GITHUB_ISSUE = 'wopee_create_github_issue' used to identify this tool by name.
      WOPEE_CREATE_GITHUB_ISSUE = "wopee_create_github_issue",
    }
  • The GraphQL mutation 'CreateGitHubIssue' that sends projectUuid, title, body, and labels to the backend and returns url, number, and title.
    export const CreateGitHubIssue = `
      mutation CreateGitHubIssue($projectUuid: ID!, $title: String!, $body: String!, $labels: [String!]) {
        createGitHubIssue(projectUuid: $projectUuid, title: $title, body: $body, labels: $labels) {
          url
          number
          title
        }
      }
    `;
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses that issue is created in linked repo and requires integration. Does not mention return value, error handling, or potential side effects, though creation is generally safe.

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 with no redundant information. Purpose, use cases, and prerequisites are front-loaded. Each sentence serves a distinct role.

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?

Simple tool with 3 params and no output schema. Description covers purpose, use scenarios, and prerequisites. Missing mention of return value or success indication, but overall adequate for the complexity.

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?

Input schema has 100% description coverage, so baseline 3. Description adds no new semantic meaning beyond schema; it only provides context. No additional parameter details.

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?

Clearly states 'Create a new GitHub issue in the project's connected repository' with specific verb and resource. Lists concrete use cases (bug reports, test failures, action items). Sibling tools have different purposes, so well differentiated.

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?

Explicitly says when to use (reporting bugs, tracking failures, action items) and mentions prerequisites (GitHub integration and WOPEE_PROJECT_UUID). Lacks explicit 'not for' cases, but context is sufficient.

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