Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

create_test_plan

Create a test plan in TestCollab with optional test cases, configurations, and assignments. Automates the creation process including bulk-add and assignment.

Instructions

Create a test plan in TestCollab using a single MCP tool call.

Before calling this tool:

  • Ask follow-up questions for missing required information.

  • Do not infer or auto-generate required values like project_id.

Execution flow:

  1. POST /testplans

  2. POST /testplantestcases/bulkAdd (optional)

  3. POST /testplanconfigurations (optional)

  4. POST /testplans/assign (optional)

Optional:

  • project_id

  • title (defaults to "Test Plan DD Month YYYY HH:mm:ss" if omitted)

  • description

  • priority (0=Low, 1=Normal, 2=High)

  • test_plan_folder (ID or title)

  • release (ID or title)

  • start_date, end_date

  • custom_fields

  • test_cases (test_case_ids/selector/assignee; assignee supports user ID/"me"/name)

  • configurations

  • assignment (supports user IDs/"me"/names; if user says "assign to me", use "me")

Example: { "project_id": 16, "title": "Release 2.9 Regression", "priority": 1, "test_cases": { "test_case_ids": [101, 102, 103] }, "configurations": [ [{ "field": "Browser", "value": "Chrome" }, { "field": "OS", "value": "Windows" }] ], "assignment": { "executor": "team", "assignment_criteria": "testCase", "assignment_method": "automatic", "user_ids": [27, 31] } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID (optional if TC_DEFAULT_PROJECT is set)
titleNoTest plan title (optional; defaults to "Test Plan DD Month YYYY HH:mm:ss")
descriptionNoTest plan description (HTML supported)
priorityNoPriority: 0=Low, 1=Normal, 2=High
test_plan_folderNoTest plan folder ID or title (null to place at root)
releaseNoRelease ID or title
start_dateNoPlanned start date (YYYY-MM-DD)
end_dateNoPlanned end date (YYYY-MM-DD)
custom_fieldsNoArray of test plan custom field values
test_casesNoTest cases to bulk-add immediately after plan creation
configurationsNoConfiguration matrix to attach to the test plan
assignmentNoAssignment payload to execute after creation
Behavior4/5

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

With no annotations, the description carries full burden. It details the execution flow (4 POST steps), optional parameters, defaults (title), and behavior for assignee and assignment. It could mention side effects like notifications but overall is transparent.

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 well-structured with sections (prerequisites, execution flow, parameter details, example). It's somewhat lengthy but each part adds value. Could be slightly leaner, but front-loaded and clear.

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 12 parameters, nested objects, no output schema, and complex behavior, the description covers prerequisites, flow, parameters with examples, and defaults. It lacks potential error conditions or permissions but is largely complete.

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 value: clarifies assignee supports 'me'/names, relationship between test_cases and assignment, and provides example JSON. Enhances understanding beyond schema.

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 test plan in TestCollab using a single MCP tool call.' It distinguishes from siblings (e.g., update_test_plan, delete_test_plan) by focusing on creation and detailing the multi-step execution flow.

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?

The description provides explicit prerequisites ('Ask follow-up questions for missing required information', 'Do not infer or auto-generate required values like project_id') and an example. It lacks explicit when-not-to-use guidance but the context of creation vs update is implicit.

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/TCSoftInc/testcollab-mcp-server'

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