mcp-testops

Overview Schema Source Related Servers Discussions Admin

create_launch

Create a test launch in Allure TestOps by specifying a name and optional project, release, tags, links, and autoclose settings; receive the launch ID and project details.

Instructions

Create a launch and return {ok, id, name, projectId}.

tags_json: [{"id": 3, "name": "regress"}]; links_json: [{"name": "JIRA", "type": "issue", "url": "https://jira/browse/ABC-1"}].

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`autoclose`	No
`tags_json`	No
`links_json`	No
`project_id`	No
`release_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Nov 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that creation returns {ok, id, name, projectId}; it says nothing about what autoclose does, whether project_id defaults to a current context, whether creation is idempotent, or what happens on invalid references.

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 text is short and front-loads the action and return shape, with examples kept tight. The semicolon-separated inline format is slightly awkward but nothing is wasted.

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?

Down-adjusted to 3: for a six-parameter mutation tool with no annotations, the definition is thin. It gives good guidance on the two JSON-string parameters, but omits how the remaining optional parameters affect behavior, and its return-value statement is substantially redundant with the existing output schema.

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 0% across six parameters, so the description must compensate. It does add genuine value by showing the exact JSON string shape expected for tags_json and links_json, but it leaves autoclose, project_id, release_id, and the required name parameter entirely unexplained.

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 opens with a specific verb and resource ("Create a launch") and even names the returned fields, so the core action is unambiguous. It does not differentiate itself from siblings such as create_test_plan or list_launches, so an agent must infer that this is specifically the launch-creation primitive.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g., that project_id/release_id must already exist), and no mention of any sibling. Usage is only implied by the verb "Create".

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