testit-mcp-server

create_test_run

Creates an empty test run in a project in NotStarted state, accepting optional payload fields for attachments, links, tags, and launch details.

Instructions

Create an empty test run in a project (state NotStarted). Extra CreateEmptyTestRunApiModel fields (attachments, links) can be passed in "payload".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_test_run"
  }
}

Input Schema

Name	Required	Description
`name`	No
`tags`	No
`payload`	No
`projectId`	No	Project UUID (defaults to TESTIT_PROJECT_ID).
`description`	No
`projectName`	No	Project name (alternative to projectId).
`launchSource`	No	Free-form launch source, e.g. CI job URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare write, non-idempotent, non-destructive, open-world behavior. The description adds two useful facts beyond them: the run is created in state NotStarted, and extra CreateEmptyTestRunApiModel fields (attachments, links) flow through the opaque 'payload' object. It says nothing about return value or auth requirements, so a 3.

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?

Two short sentences, front-loaded with the action and the resulting state; the payload escape hatch comes second. No filler, though the capitalization of 'payload' mid-sentence is slightly bumpy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter create tool with no output schema and open-world hint, the definition leaves gaps: it does not say what is returned (presumably the created run identifier) or what happens on duplicate names. It is adequate to invoke but not to predict results.

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 43%, so half the parameters are undocumented structurally. The description compensates for the hardest one by explaining that 'payload' carries additional CreateEmptyTestRunApiModel fields such as attachments and links, but adds no meaning for name, tags, or description.

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?

States a specific verb and resource ('Create an empty test run in a project') plus the resulting state (NotStarted). The word 'empty' implicitly separates it from the from_autotests / from_test_points / from_work_items siblings, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'empty' suggests use when you are not deriving the run from autotests, test points, or work items. There is no explicit when-to-use statement, no prerequisites, and no named alternative for the populate-from-source case.

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

Deploy Server