Skip to main content
Glama

Run Newman collection

run_newman_collection

Runs local or remote Postman/Newman collections with configurable variables, timeouts, SSL settings, iterations, and state exports, enabling automated API tests and result capture.

Instructions

Runs a local or remote collection with full control over variables, timeouts, SSL, iterations, and state export.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collectionSource": "<collectionSource>"
    },
    "name": "run_newman_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoFolder(s) to run (--folder)
envVarsNoInline environment variables (--env-var)
exportsNoExport files
globalVarsNoInline global variables (--global-var)
sslOptionsNoSSL options
globalsPathNoGlobals path (-g)
iterationCountNoNumber of iterations (-n)
environmentPathNoEnvironment path (-e)
collectionSourceYesCollection (path, https URL, or Postman UID)
executionControlNoExecution controls
iterationDataPathNoIteration data path (-d)

Output Schema

NameRequiredDescriptionDefault
statsYes
abortedYes
successYes
timingsYes
failuresYes
truncatedYes
consoleLogsYes
exportedFilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context that it executes real collections with controllable timeouts, SSL handling and state export, but omits what an operator most needs: credential requirements for remote/Postman UID sources, expected runtime, and what happens on failure beyond the bail option.

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?

A single front-loaded sentence with the verb first and the capability list trailing; no filler. The clause 'with full control over...' is slightly promotional but does convey the breadth of configuration in few 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?

An output schema exists, so return values need not be explained, and the description correctly signals this is a full execution engine rather than a thin wrapper. However, for an 11-parameter open-world execution tool it should mention authentication for remote sources and the consequence of a run (side effects on target systems), which are absent.

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 description coverage is 100% with 11 documented parameters including Newman CLI flags, so the schema does the heavy lifting. The description only enumerates parameter categories (variables, timeouts, SSL, iterations, exports) without adding format, precedence or interaction rules, which is baseline behavior when the schema is complete.

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 gives a specific verb+resource ('Runs a ... collection') and adds meaningful scope: local or remote sources and the dimensions of control (variables, timeouts, SSL, iterations, state export). An agent can tell this is the execution tool rather than a reporting or inspection one, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to call this after validating a collection, or to use analyze_newman_failure / generate_newman_report afterwards. Prerequisites for remote or Postman UID sources (API key, CLI availability) are also unstated, leaving usage entirely implied.

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