Skip to main content
Glama

list_tests

Retrieve and filter test runs from the QIT CLI for WordPress/WooCommerce plugins. Use status, test type, or extension filters to find specific results.

Instructions

List test runs with optional filters. Default per_page is 10 to reduce response size.

⚠️ QIT CLI not detected. QIT CLI not found. Please install it using one of these methods:

  1. Via Composer (recommended): composer require woocommerce/qit-cli --dev

  2. Set QIT_CLI_PATH environment variable: export QIT_CLI_PATH=/path/to/qit

  3. Ensure 'qit' is available in your system PATH

For more information, visit: https://github.com/woocommerce/qit-cli

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by test status
test_typeNoFilter by test type (e.g., 'security', 'e2e')
extensionNoFilter by extension slug
per_pageNoMaximum number of results to return (default: 10)

Implementation Reference

  • Handler function that constructs flags from input arguments and invokes the underlying 'list-tests' CLI command via executeAndFormat.
    handler: async (args: {
      status?: string;
      test_type?: string;
      extension?: string;
      per_page?: number;
    }) => {
      // Default per_page to 10 to prevent large responses
      const perPage = args.per_page ?? 10;
    
      const flags: Record<string, string | boolean | undefined> = {
        test_status: args.status,
        test_types: args.test_type,
        extensions: args.extension,
        per_page: perPage.toString(),
      };
    
      const cmdArgs = buildArgs("list-tests", [], flags);
      return executeAndFormat(cmdArgs);
    },
  • Zod schema for input validation, defining optional filters for status, test_type, extension, and per_page limit.
    inputSchema: z.object({
      status: z
        .enum(["pending", "running", "success", "failed", "warning"])
        .optional()
        .describe("Filter by test status"),
      test_type: z
        .string()
        .optional()
        .describe("Filter by test type (e.g., 'security', 'e2e')"),
      extension: z
        .string()
        .optional()
        .describe("Filter by extension slug"),
      per_page: z
        .number()
        .optional()
        .describe("Maximum number of results to return (default: 10)"),
    }),
  • Complete definition of the 'list_tests' tool, including name, description, input schema, and handler, within the testResultsTools export.
    list_tests: {
      name: "list_tests",
      description: "List test runs with optional filters. Default per_page is 10 to reduce response size.",
      inputSchema: z.object({
        status: z
          .enum(["pending", "running", "success", "failed", "warning"])
          .optional()
          .describe("Filter by test status"),
        test_type: z
          .string()
          .optional()
          .describe("Filter by test type (e.g., 'security', 'e2e')"),
        extension: z
          .string()
          .optional()
          .describe("Filter by extension slug"),
        per_page: z
          .number()
          .optional()
          .describe("Maximum number of results to return (default: 10)"),
      }),
      handler: async (args: {
        status?: string;
        test_type?: string;
        extension?: string;
        per_page?: number;
      }) => {
        // Default per_page to 10 to prevent large responses
        const perPage = args.per_page ?? 10;
    
        const flags: Record<string, string | boolean | undefined> = {
          test_status: args.status,
          test_types: args.test_type,
          extensions: args.extension,
          per_page: perPage.toString(),
        };
    
        const cmdArgs = buildArgs("list-tests", [], flags);
        return executeAndFormat(cmdArgs);
      },
    },
  • Aggregation of all tools including testResultsTools (which contains list_tests) into allTools export.
    export const allTools = {
      ...authTools,
      ...testExecutionTools,
      ...testResultsTools,
  • src/server.ts:29-29 (registration)
    Final registration of all tools (including list_tests) into the MCP server tools array.
    const tools = Object.entries(allTools).map(([_, tool]) => ({
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'Default per_page is 10 to reduce response size' which is useful behavioral context about pagination defaults. However, it fails to describe important behaviors like whether this is a read-only operation, what the response format looks like, whether results are paginated beyond the per_page setting, or any rate limits. The QIT CLI warning is installation guidance, not tool behavior disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is poorly structured with wasted content. The first sentence is relevant tool description, but the remaining 80% is QIT CLI installation troubleshooting that doesn't belong in a tool description. This is not conciseness - it's inappropriate content inclusion that dilutes the actual tool information.

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 4-parameter listing tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'test runs' are in this context, doesn't describe the return format or structure, and doesn't provide context about how this fits with the sibling tools. The QIT CLI warning is irrelevant to the tool's actual functionality and doesn't compensate for the missing contextual information.

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 the schema already documents all 4 parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'optional filters' which is already clear from the schema, and mentions the default per_page value which the schema also documents. No additional parameter semantics are provided beyond what's in the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'List test runs with optional filters' which clearly states the verb (list) and resource (test runs). However, it doesn't distinguish this from other list-related tools like 'list_environments' or 'list_extensions' - it's generic about what makes this listing operation unique. The purpose is understandable but lacks sibling differentiation.

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?

The description provides no guidance about when to use this tool versus alternatives. There's no mention of when this should be used instead of 'get_test_report' or 'get_test_result', nor does it explain the relationship to 'run_test' or 'run_test_group'. The only usage information is about QIT CLI installation issues, which isn't actual usage guidance for the tool itself.

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/woocommerce/qit-mcp'

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