Skip to main content
Glama

create_manual_run

Create a new manual test run. Specify project, name, and optionally link to a release, assign tags, or select specific test cases or suites.

Instructions

Create a new manual test run. Requires write permission. selectionMode controls which test cases are included: 'all' (default — every case in the project) or 'selected' (use testCaseIds and/or suiteIds to scope). releaseId attaches the run to a release. note accepts rich HTML. IMPORTANT: tags must be a JSON array of strings here — e.g. ["smoke","regression"] — NOT the comma-separated form that list_manual_runs accepts as a filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (required).
nameYesRun name (required).
noteNoRich HTML note.
environmentNoEnvironment label, e.g. 'Staging'.
releaseIdNoAttach run to this release.
stateNoWorkflow state (default 'new'). Either canonical ('in_progress') or display ('In Progress') form — server normalizes to lowercase+underscored so UI colors render correctly.
selectionModeNoDefault 'all'.
testCaseIdsNo
suiteIdsNo
includeUnsortedNo
forecastNo
tagsNoArray of tag strings, e.g. ["smoke","regression"]. NOT a comma-separated string.
linkedIssuesNoArray of linked-issue objects (same shape list_manual_runs returns).
attachmentsNoArray of attachment objects or URLs.
linksNoArray of link objects.

Implementation Reference

  • handleCreateManualRun: The handler function that creates a manual test run. It extracts the API key, validates required args (projectId, name), builds the endpoint URL, and sends a POST request with the remaining args as the body. Returns the JSON response wrapped in MCP content format.
    export async function handleCreateManualRun(args?: CreateManualRunArgs) {
      const token = getApiKey(args);
      if (!token) {
        throw new Error(
          "Missing TESTDINO_PAT environment variable. Configure it in your .cursor/mcp.json under 'env'."
        );
      }
      if (!args?.projectId) throw new Error("projectId is required");
      if (!args?.name) throw new Error("name is required");
    
      try {
        const { projectId, ...body } = args;
        const url = endpoints.createManualRun(String(projectId));
        const response = await apiRequestJson<unknown>(url, {
          method: "POST",
          headers: { Authorization: `Bearer ${token}` },
          body,
        });
        return {
          content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        throw new Error(`Failed to create manual run: ${msg}`);
      }
    }
  • createManualRunTool: Schema registration object for the 'create_manual_run' tool. Includes the name (create_manual_run), description, and inputSchema defining all parameters: projectId (required), name (required), note, environment, releaseId, state, selectionMode, testCaseIds, suiteIds, includeUnsorted, forecast, tags, linkedIssues, attachments, links.
    export const createManualRunTool = {
      name: "create_manual_run",
      description:
        "Create a new manual test run. Requires write permission. selectionMode controls which test cases are included: 'all' (default — every case in the project) or 'selected' (use testCaseIds and/or suiteIds to scope). releaseId attaches the run to a release. note accepts rich HTML. IMPORTANT: tags must be a JSON array of strings here — e.g. [\"smoke\",\"regression\"] — NOT the comma-separated form that list_manual_runs accepts as a filter.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project ID (required)." },
          name: { type: "string", description: "Run name (required)." },
          note: { type: "string", description: "Rich HTML note." },
          environment: {
            type: "string",
            description: "Environment label, e.g. 'Staging'.",
          },
          releaseId: { type: "string", description: "Attach run to this release." },
          state: {
            type: "string",
            description:
              "Workflow state (default 'new'). Either canonical ('in_progress') or display ('In Progress') form — server normalizes to lowercase+underscored so UI colors render correctly.",
          },
          selectionMode: {
            type: "string",
            enum: ["all", "selected"],
            description: "Default 'all'.",
          },
          testCaseIds: { type: "array", items: { type: "string" } },
          suiteIds: { type: "array", items: { type: "string" } },
          includeUnsorted: { type: "boolean" },
          forecast: {},
          tags: {
            type: "array",
            items: { type: "string" },
            description:
              'Array of tag strings, e.g. ["smoke","regression"]. NOT a comma-separated string.',
          },
          linkedIssues: {
            type: "array",
            items: {},
            description:
              "Array of linked-issue objects (same shape list_manual_runs returns).",
          },
          attachments: {
            type: "array",
            items: {},
            description: "Array of attachment objects or URLs.",
          },
          links: {
            type: "array",
            items: {},
            description: "Array of link objects.",
          },
        },
        required: ["projectId", "name"],
      },
    };
  • src/index.ts:306-310 (registration)
    Tool dispatch: When the tool name equals 'create_manual_run', the server invokes handleCreateManualRun with the provided args.
    if (name === "create_manual_run") {
      return await handleCreateManualRun(
        args as Parameters<typeof handleCreateManualRun>[0]
      );
    }
  • src/index.ts:59-60 (registration)
    Imports createManualRunTool and handleCreateManualRun into the main server file from the manual-runs module.
    createManualRunTool,
    handleCreateManualRun,
  • Endpoint builder: creates the URL '/api/mcp/manual-runs/{projectId}' for the POST request when creating a manual run.
    createManualRun: (projectId: string): string => {
      const baseUrl = getBaseUrl();
      return `${baseUrl}/api/mcp/manual-runs/${projectId}`;
    },
Behavior4/5

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

Despite no annotations, the description discloses important behaviors: requires write permission, explains selectionMode options, warns about tags format mismatch with list_manual_runs, and notes state normalization. This adds good context beyond the schema.

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?

The description is concise with 5 sentences covering essential points. It is front-loaded with the primary purpose and permission. While not bulleted, the information density is good and no unnecessary words.

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?

Given 15 parameters and no output schema, the description covers key aspects (permission, selectionMode, tags, state, note) but omits details about return value, some less common parameters (forecast, attachments), and potential error conditions. It is adequate for typical use but incomplete for edge cases.

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?

The description adds meaningful insights for several parameters: explains selectionMode's effect with 'all' vs 'selected', clarifies tags format (JSON array not comma-separated), and describes state normalization. This goes beyond the schema's enum and type info.

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 manual test run.' with a specific verb and resource. It distinguishes from sibling tools like update_manual_run or list_manual_runs by focusing on creation.

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 does not provide guidance on when to use this tool over alternatives (e.g., when to use create_manual_run vs create_manual_test_case). It only mentions a write permission prerequisite, which is necessary but not comparative.

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