Skip to main content
Glama

Validate Postman collection

validate_postman_collection
Read-only

Validates Postman collections statically by checking JSON, schema, script syntax, forbidden APIs, and undefined variables to catch issues before running.

Instructions

Instant static validation (no model or HTTP requests). Checks JSON, schema, script syntax, forbidden APIs, and undefined variables.

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": "validate_postman_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
globalsPathNoGlobals path
environmentPathNoEnvironment path
collectionSourceYesCollection (path, https URL, or Postman UID)
iterationDataPathNoIteration data path

Output Schema

NameRequiredDescriptionDefault
validYes
issuesYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the check is static, instant, and performs no model calls or HTTP requests, and it lists the specific categories of problems detected. One caveat: the schema allows collectionSource to be an https URL, which sits in tension with the claim of "no HTTP requests"; the description does not resolve how remote sources are retrieved.

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 dense sentence, front-loaded with the key differentiator ("instant static validation") followed by the parenthetical and the enumerated checks. Nothing is wasted, though the unqualified "no HTTP requests" phrasing costs a little clarity given URL support.

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 no explanation, and all parameters are schema-documented. What is missing for a validation tool in a crowded sibling set is how it relates to inspect_postman_collection and run_newman_collection, plus how an https collectionSource squares with the no-HTTP claim.

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%, so the four parameters (collectionSource, globalsPath, environmentPath, iterationDataPath) are already documented in the schema. The description adds no meaning about how these inputs affect what is validated (e.g. whether environment/globals are used for undefined-variable resolution), which is the one place extra text would have earned 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?

States a specific verb and resource ("validate" a Postman collection) and enumerates the checks performed: JSON, schema, script syntax, forbidden APIs, undefined variables. That is well beyond tautology. It does not, however, distinguish the scope from the sibling inspect_postman_collection, so an agent must guess which is the lighter-weight option.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: "instant static validation (no model or HTTP requests)" signals a fast, cheap pre-flight check that plausibly precedes run_newman_collection, but no condition, prerequisite, or named alternative is stated. There is no explicit when-not guidance.

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