Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

update_suite

Modify test suite details like title or description in TestCollab. Provide the suite ID and optional fields to update.

Instructions

Update an existing test suite in TestCollab. Only provided fields will be updated.

Required: id (suite ID) Optional: project_id, title, description

Note: To move a suite to a different parent, use the move_suite tool instead.

Example: { "id": 42, "title": "Renamed Suite", "description": "Updated description" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSuite ID to update (required)
project_idNoProject ID (optional if TC_DEFAULT_PROJECT is set)
titleNoNew suite title
descriptionNoNew suite description (null to clear)

Implementation Reference

  • The handler function `handleUpdateSuite` that executes the update logic.
    export async function handleUpdateSuite(args: {
      id: number;
      project_id?: number;
      title?: string;
      description?: string | null;
    }): Promise<{ content: Array<{ type: "text"; text: string }> }> {
      try {
        const projectId = resolveProjectId(args.project_id);
        if (!projectId) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({
                  error: {
                    code: "MISSING_PROJECT_ID",
                    message:
                      "No project_id provided and no default project configured. Set TC_DEFAULT_PROJECT or pass project_id.",
                  },
                }),
              },
            ],
          };
        }
    
        // Check that at least one field is being updated
        if (args.title === undefined && args.description === undefined) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({
                  error: {
                    code: "NO_FIELDS_TO_UPDATE",
                    message:
                      "No fields provided to update. Specify at least one of: title, description.",
                  },
                }),
              },
            ],
          };
        }
    
        const client = getApiClient();
        const result = await client.updateSuite(args.id, {
          projectId,
          title: args.title,
          description: args.description,
        });
    
        // Invalidate project context cache
        clearProjectContextCache();
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                success: true,
                suite: result,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                error: {
                  code: "UPDATE_SUITE_FAILED",
                  message:
                    error instanceof Error ? error.message : "Unknown error",
                },
              }),
            },
          ],
        };
      }
    }
  • Zod schema definition for `update_suite` inputs.
    export const updateSuiteSchema = z.object({
      id: z.number().describe("Suite ID to update (required)"),
      project_id: z
        .number()
        .optional()
        .describe("Project ID (optional if TC_DEFAULT_PROJECT is set)"),
      title: z.string().min(1).optional().describe("New suite title"),
      description: z
        .union([z.string(), z.null()])
        .optional()
        .describe("New suite description (null to clear)"),
    });
  • The tool object `updateSuiteTool` providing the tool metadata.
    export const updateSuiteTool = {
      name: "update_suite",
      description: `Update an existing test suite in TestCollab. Only provided fields will be updated.
    
    Required: id (suite ID)
    Optional: project_id, title, description
    
    Note: To move a suite to a different parent, use the move_suite tool instead.
    
    Example: { "id": 42, "title": "Renamed Suite", "description": "Updated description" }`,
    };
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the partial-update behavior ('Only provided fields will be updated'), which is critical behavioral context. However, it lacks disclosure of side effects, idempotency, authentication requirements, or what constitutes a successful update response.

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?

Excellent structure with purpose front-loaded, followed by behavioral note, parameter summary, alternative tool reference, and example. Every sentence serves a distinct purpose. No redundancy or fluff.

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 the simple 4-parameter flat schema and lack of output schema, the description covers the essential usage patterns well. However, as a mutation tool with zero annotations, it could benefit from mentioning idempotency, return value structure, or permission requirements 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?

Schema coverage is 100%, establishing a baseline of 3. The description adds value by grouping parameters into Required/Optional categories and providing a concrete JSON example, but does not add deeper semantic meaning (e.g., business rules for title format, or when project_id is necessary) beyond what the schema already documents.

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 explicitly states 'Update an existing test suite in TestCollab' with a specific verb and resource. It distinguishes from move_suite by explicitly noting that tool should be used for parent moves instead, and implies distinction from create_suite by specifying 'existing'.

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?

Provides explicit guidance on when NOT to use this tool ('To move a suite to a different parent, use the move_suite tool instead'). It also clarifies the partial update semantics ('Only provided fields will be updated'). Could be improved by explicitly contrasting with create_suite for new suites.

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