testit-mcp-server

search_test_results

Read-only

Retrieve filtered test results using outcomes, run IDs, status codes, configuration IDs, or a raw query, with pagination and sorting for targeted analysis.

Instructions

Search test results. Typed fields are merged with an optional raw "query" (TestResultsFilterApiModel) for advanced fields.

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": "search_test_results"
  }
}

Input Schema

Name	Required	Description
`name`	No
`page`	No	1-based page number; alternative to skip. Uses "size" (default 50).
`size`	No	Page size for "page"; alias of take.
`skip`	No	Number of items to skip (offset).
`take`	No	Max number of items to return.
`query`	No
`orderBy`	No	Sort expression, e.g. "createdDate desc".
`outcomes`	No
`testRunIds`	No
`searchField`	No	Field name to search in.
`searchValue`	No	Value to search for in searchField.
`statusCodes`	No
`configurationIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the meaningful behavioral detail that typed fields and a raw filter model are merged into one filter, but it does not say how conflicts resolve, what a bare call returns, or any result limits.

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 with the purpose front-loaded and the filter-merge caveat second. No wasted wording, though the second sentence is dense and slightly ambiguous.

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?

For a 13-parameter, zero-required tool with a nested filter object and no output schema, the description leaves too much open: default behavior with no filters, interaction between page/skip and take/size, and the shape of returned results are all unaddressed.

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 54%, and the "query" object has no schema description at all, so the note that it is a TestResultsFilterApiModel merged with typed fields genuinely adds value. However, the merge precedence and what constitutes an "advanced field" remain unspecified, and most of the other 13 parameters get no mention.

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 gives a clear verb and resource ("Search test results") plus a note about how the raw query object relates to typed fields. It does not distinguish this tool from result-retrieval siblings such as get_test_run_results or list_test_suite_test_results, so the agent must infer scope.

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 versus the many sibling result tools, no prerequisites, and no exclusions. The only guidance is that "query" handles advanced fields, which is parameter-level rather than tool-selection guidance.

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

Deploy Server