Skip to main content
Glama

create_manual_test_suite

Creates a manual test suite folder to organize test cases. Supports nesting under a parent suite for hierarchical structure.

Instructions

Create a new test suite folder to organize test cases. Use this to create a logical grouping for related test cases. Suites can be nested by providing a parentSuiteId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (Required). The TestDino project identifier.
nameYesSuite name (Required). A descriptive name for the test suite.
descriptionNoDescription of the test suite.
parentSuiteIdNoOptional parent suite ID to create this suite as a child of another suite. If not provided, creates a root-level suite.

Implementation Reference

  • The handler function that executes the create_manual_test_suite tool logic. It validates args (projectId, name), builds a request body, calls the API endpoint via POST, and returns the response.
    export async function handleCreateManualTestSuite(
      args?: CreateManualTestSuiteArgs
    ) {
      // Read PAT from environment variable (set in mcp.json) or from args
      const token = getApiKey(args);
    
      if (!token) {
        throw new Error(
          "Missing TESTDINO_PAT environment variable. " +
            "Please configure it in your .cursor/mcp.json file under the 'env' section."
        );
      }
    
      // Validate required parameters
      if (!args?.projectId) {
        throw new Error("projectId is required");
      }
      if (!args?.name) {
        throw new Error("name is required");
      }
    
      try {
        const body: CreateManualTestSuiteBody = {
          projectId: String(args.projectId),
          name: String(args.name),
        };
    
        // Add optional fields
        if (args?.description) {
          body.description = String(args.description);
        }
        if (args?.parentSuiteId) {
          body.parentSuiteId = String(args.parentSuiteId);
        }
    
        const createManualTestSuiteUrl = endpoints.createManualTestSuite(
          String(args.projectId)
        );
    
        const response = await apiRequestJson<unknown>(createManualTestSuiteUrl, {
          method: "POST",
          headers: {
            Authorization: `Bearer ${token}`,
          },
          body,
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        throw new Error(`Failed to create manual test suite: ${errorMessage}`);
      }
    }
  • TypeScript interfaces (CreateManualTestSuiteArgs, CreateManualTestSuiteBody) and the tool definition object (createManualTestSuiteTool) with inputSchema defining projectId (required), name (required), description (optional), and parentSuiteId (optional).
    interface CreateManualTestSuiteArgs {
      projectId: string;
      name: string;
      description?: string;
      parentSuiteId?: string;
    }
    
    interface CreateManualTestSuiteBody {
      projectId: string;
      name: string;
      description?: string;
      parentSuiteId?: string;
    }
    
    export const createManualTestSuiteTool = {
      name: "create_manual_test_suite",
      description:
        "Create a new test suite folder to organize test cases. Use this to create a logical grouping for related test cases. Suites can be nested by providing a parentSuiteId.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "Project ID (Required). The TestDino project identifier.",
          },
          name: {
            type: "string",
            description:
              "Suite name (Required). A descriptive name for the test suite.",
          },
          description: {
            type: "string",
            description: "Description of the test suite.",
          },
          parentSuiteId: {
            type: "string",
            description:
              "Optional parent suite ID to create this suite as a child of another suite. If not provided, creates a root-level suite.",
          },
        },
        required: ["projectId", "name"],
      },
    };
  • Re-exports the createManualTestSuiteTool and handleCreateManualTestSuite from the implementation file, making them available to the main server.
    export {
      createManualTestSuiteTool,
      handleCreateManualTestSuite,
    } from "./manual-testsuites/create-manual-test-suite.js";
  • src/index.ts:112-112 (registration)
    Tool is included in the tools array for MCP server capability registration.
    createManualTestSuiteTool,
  • src/index.ts:267-271 (registration)
    The tool dispatch logic: when tool name is 'create_manual_test_suite', it calls handleCreateManualTestSuite with the parsed args.
    if (name === "create_manual_test_suite") {
      return await handleCreateManualTestSuite(
        args as Parameters<typeof handleCreateManualTestSuite>[0]
      );
    }
  • URL builder helper: constructs the POST endpoint URL as `${baseUrl}/api/mcp/manual-tests/${projectId}/test-suites`.
    /**
     * Create manual test suite
     * POST /api/mcp/manual-tests/:projectId/test-suites
     */
    createManualTestSuite: (projectId: string): string => {
      const baseUrl = getBaseUrl();
      return `${baseUrl}/api/mcp/manual-tests/${projectId}/test-suites`;
    },
Behavior2/5

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

No annotations are provided, so the description must disclose side effects. It does not mention what the tool returns (no output schema), whether it requires permissions, or if names must be unique. Behavioral context like idempotency or error handling is absent.

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

Conciseness5/5

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

Two short, clear sentences with no wasted words. Front-loaded with the primary purpose.

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?

The description covers the main purpose and nesting, but fails to explain the return value or any behavioral constraints (e.g., uniqueness of names). Given the lack of output schema and annotations, the description should provide more context to be fully complete.

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?

The input schema has 100% description coverage for all 4 parameters. The description adds minimal value by mentioning parentSuiteId for nesting, but otherwise restates schema info. Baseline score of 3 is appropriate.

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?

The description clearly states 'Create a new test suite folder to organize test cases,' specifying the action (create) and resource (test suite folder). It differentiates from siblings like create_manual_test_case and create_manual_run.

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?

It explains when to use the tool ('logical grouping for related test cases') and mentions nesting with parentSuiteId. However, it does not explicitly exclude alternatives or provide when-not-to-use guidance.

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/testdino-hq/testdino-mcp'

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