Skip to main content
Glama

Create GitHub issue

wopee_create_github_issue

Creates a GitHub issue to report bugs, track test failures, or record action items; add an executed test case UUID to include failing-step evidence.

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. For a failed test, pass its executedTestCaseUuid so the issue carries the run's evidence (failing step, expected vs actual, screenshot, report link). The issue is created by the Wopee.io GitHub App and names the requester in its body. Requires a GitHub repository linked to the project and WOPEE_PROJECT_UUID to be set.

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": {
      "title": "<title>"
    },
    "name": "wopee_create_github_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoThe body/description of the GitHub issue (supports Markdown). Kept verbatim, above anything Wopee.io adds from the test run.
titleYesThe title of the GitHub issue
labelsNoOptional labels to apply to the issue (e.g., ['bug', 'testing'])
executedTestCaseUuidNoUUID of the executed test case the issue is about (the executedTestCaseUuid shown by wopee_fetch_recent_executions and wopee_dispatch_agent, or uuid in wopee_fetch_executed_test_cases). When set, Wopee.io adds the failing step, expected vs actual, the failing step's screenshot and a link to the run in Commander, so the body only needs your own analysis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.32.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed3 schema fields changedv1.31.0
    • changedInput schema / properties / body / description
      Previous value: -"The body/description of the GitHub issue (supports Markdown)"New value: +"The body/description of the GitHub issue (supports Markdown). Kept verbatim, above anything Wopee.io adds from the test run."
    • addedInput schema / properties / executedTestCaseUuid
      Added value: +{
      +  "description": "UUID of the executed test case the issue is about (the executedTestCaseUuid shown by wopee_fetch_recent_executions and wopee_dispatch_agent, or uuid in wopee_fetch_executed_test_cases). When set, Wopee.io adds the failing step, expected vs actual, the failing step's screenshot and a link to the run in Commander, so the body only needs your own analysis.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "title",
      -  "body"
      -]New value: +[
      +  "title"
      +]
  3. Addedv1.26.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses who authors the issue (the Wopee.io GitHub App), that the requester is named in the body, that the body is kept verbatim above Wopee.io additions, and two hard prerequisites: a linked GitHub repository and WOPEE_PROJECT_UUID being set. That is substantial behavioral context an agent cannot get from the annotations alone.

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?

Front-loaded with the action, then use cases, then the failed-test special case, then prerequisites — a logical order with no filler. There is mild duplication with the schema's own description of executedTestCaseUuid, which keeps it from a perfect score.

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 four-parameter creation tool with no output schema, the definition covers purpose, use cases, the key optional parameter's effect, authorship, and both prerequisites. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, so all four parameters, including the executedTestCaseUuid enrichment behavior, are already documented in the schema. The description restates the uuid guidance and the evidence it attaches without adding syntax, format, or constraint detail beyond the schema, so baseline 3 applies.

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?

"Create a new GitHub issue in the project's connected repository" gives a specific verb (create), resource (GitHub issue), and scope (project's connected repo). It is immediately distinguishable from the sibling tools, which all deal with Wopee.io artifacts and executions rather than GitHub issues.

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 names concrete use cases (report bugs found during testing, track test failures, create action items from chat) and gives a conditional rule: for a failed test, pass executedTestCaseUuid. It stops short of naming alternatives or exclusions, but the when-to-use guidance is clear and actionable.

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