Skip to main content
Glama

run-collection

Execute Postman API test collections with Newman to validate endpoints and get detailed results. Specify collection path, environment, globals, and iteration count.

Instructions

Run a Postman Collection using Newman

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesPath or URL to the Postman collection
environmentNoOptional path or URL to environment file
globalsNoOptional path or URL to globals file
iterationCountNoOptional number of iterations to run

Implementation Reference

  • Core handler function that executes the Newman CLI to run the Postman collection, processes the run summary and failures into a structured TestResult.
    async runCollection(options: CollectionRunOptions): Promise<TestResult> {
        return new Promise((resolve, reject) => {
            const startTime = new Date().toISOString();
            
            newman.run({
                collection: options.collection,
                environment: options.environment,
                globals: options.globals,
                iterationCount: options.iterationCount,
                reporters: 'cli'
            }, (err, summary) => {
                if (err) {
                    reject(err);
                    return;
                }
    
                const endTime = new Date().toISOString();
                
                // Format the results
                const result: TestResult = {
                    success: summary.run.failures.length === 0,
                    summary: {
                        total: summary.run.stats.tests.total || 0,
                        failed: summary.run.stats.tests.failed || 0,
                        passed: (summary.run.stats.tests.total || 0) - (summary.run.stats.tests.failed || 0)
                    },
                    failures: (summary.run.failures || [])
                        .map(extractFailureInfo)
                        .filter((failure): failure is TestFailure => failure !== null),
                    timings: {
                        started: startTime,
                        completed: endTime,
                        duration: new Date(endTime).getTime() - new Date(startTime).getTime()
                    }
                };
    
                resolve(result);
            });
        });
    }
  • MCP CallToolRequest handler specifically for 'run-collection' tool: validates input, executes NewmanRunner.runCollection, and formats success/error responses.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
        if (request.params.name !== "run-collection") {
            throw new Error(`Unknown tool: ${request.params.name}`);
        }
    
        // Validate input
        const args = RunCollectionSchema.parse(request.params.arguments);
    
        try {
            // Run the collection
            const result = await this.runner.runCollection(args);
    
            // Format the response
            return {
                content: [{
                    type: "text",
                    text: JSON.stringify(result, null, 2)
                }]
            };
        } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            return {
                content: [{
                    type: "text",
                    text: JSON.stringify({
                        error: errorMessage,
                        success: false
                    }, null, 2)
                }],
                isError: true
            };
        }
    });
  • Zod schema for validating the input arguments to the 'run-collection' tool.
    const RunCollectionSchema = z.object({
        collection: z.string(),
        environment: z.string().optional(),
        globals: z.string().optional(),
        iterationCount: z.number().min(1).optional()
    });
  • Tool registration in ListToolsRequest handler: defines name, description, and JSON inputSchema for 'run-collection'.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: [
            {
                name: "run-collection",
                description: "Run a Postman Collection using Newman",
                inputSchema: {
                    type: "object",
                    properties: {
                        collection: {
                            type: "string",
                            description: "Path or URL to the Postman collection"
                        },
                        environment: {
                            type: "string",
                            description: "Optional path or URL to environment file"
                        },
                        globals: {
                            type: "string",
                            description: "Optional path or URL to globals file"
                        },
                        iterationCount: {
                            type: "number",
                            description: "Optional number of iterations to run"
                        }
                    },
                    required: ["collection"]
                }
            }
        ]
    }));
  • Helper function to safely parse and extract structured failure information from Newman's failure objects.
    function extractFailureInfo(failure: NewmanRunFailure): TestFailure | null {
        try {
            if (!failure.error || !failure.source?.request) {
                return null;
            }
    
            const { error, source } = failure;
            const { request } = source;
    
            // Ensure we have all required properties
            if (!error.test || !error.message || !request.method || !request.url) {
                return null;
            }
    
            return {
                name: error.test,
                error: error.message,
                request: {
                    method: request.method,
                    url: request.url.toString()
                }
            };
        } catch {
            return null;
        }
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It fails to mention critical behavioral traits such as whether this is a read-only or destructive operation, authentication requirements, rate limits, execution time, or what happens during the run (e.g., output format, error handling).

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?

The description is a single, efficient sentence with zero wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

Given the complexity of running a Postman collection (which involves execution, potential side effects, and output), the lack of annotations and output schema means the description is incomplete. It does not address what the tool returns, error conditions, or behavioral implications, leaving significant gaps for an AI agent.

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, clearly documenting all four parameters. The description adds no additional semantic information about parameters beyond what the schema provides, so it meets the baseline of 3 for adequate but not additive value.

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

Purpose4/5

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

The description clearly states the action ('Run') and the resource ('a Postman Collection using Newman'), providing a specific verb+resource combination. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.

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 on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without offering any usage instructions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools