Skip to main content
Glama

Search Test Cases

search_test_cases
Read-onlyIdempotent

Search for test cases using simple name/tag queries or advanced AQL filters to find matching test cases quickly.

Instructions

Search for test cases by name, tag, or AQL query.

Find test cases matching your search criteria. Supports simple name/tag search or advanced AQL (Allure Query Language) for complex filtering.

Simple Query Syntax (use 'query' parameter):

  • Plain text: Searches in test case names (case-insensitive)

  • tag:value: Filters by exact tag match

  • Combined: "login tag:smoke" finds test cases with "login" in name AND "smoke" tag

Important: see https://docs.qameta.io/allure-testops/advanced/aql/ for the full AQL syntax reference. AQL Syntax (use 'aql' parameter):

  • Operators: and, or, not

  • Precedence: and binds tighter than or; use parentheses to group

  • Strings are double-quoted; numbers are unquoted; booleans are true/false

  • Comparison operators: =, !=, ~= (contains), in, not in

  • Field examples: status, tag, name, createdBy, automated, layer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aqlNoRaw AQL (Allure Query Language) for complex searches. Important: see https://docs.qameta.io/allure-testops/advanced/aql/ for the full AQL syntax reference.Supports AND, OR, NOT operators, parentheses for grouping, and field filters. Strings must be double-quoted. Examples: - 'status="failed" and tag="regression"' - '(createdBy = "John" or createdBy = "Jane") and name ~= "test"' - 'tag in ["smoke", "e2e"] and automated = true' - 'not status = "Draft" and layer = "API"'
pageNoZero-based page index.
sizeNoNumber of results per page (max 100).
queryNoSimple search query. Examples: 'login flow', 'tag:smoke', 'tag:smoke tag:regression', 'authentication tag:security'. Ignored when 'aql' is provided.
project_idNoAllure TestOps project ID to list test cases from.
output_formatNoOutput format: 'json' (default) or 'plain'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesZero-based result page.
sizeYesRequested page size.
itemsYesMatching test cases.
queryYesQuery that produced these results.
totalYesTotal matching test cases.
total_pagesYesNumber of result pages.
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds behavioral details: case-insensitive name search, exact tag match, combined queries, and the precedence of 'aql' over 'query'. No contradictions with annotations.

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?

Well-structured with clear sections and examples. Slightly repetitive with AQL reference appearing both in description and schema. Efficient overall.

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?

Given 6 parameters, full schema coverage, and an existing output schema, the description adequately covers search modes, parameter interactions, and external references. Complete for use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds extra context beyond schema: explains simple query syntax with examples, clarifies interaction between 'query' and 'aql' parameters. Baseline is 3; description earns a 4.

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?

Clear verb 'Search' and resource 'test cases' with explicit search methods (name, tag, AQL). Distinguishes from siblings like 'list_test_cases' and 'get_test_case_details'.

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?

Explains two search modes (simple query vs AQL) with syntax examples and a link to AQL docs. Notes that 'query' is ignored when 'aql' is provided. However, does not explicitly contrast with 'list_test_cases' for unfiltered listing.

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/ivanostanin/lucius-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server