postman-mcp-server

create_api_version

Create a new API version by specifying schemas, collections, and optional release notes. Used to manage API lifecycle changes.

Instructions

Create a new version of an API

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": {
      "apiId": "<apiId>",
      "name": "<name>",
      "schemas": "<schemas>",
      "collections": "<collections>"
    },
    "name": "create_api_version"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Version name
`apiId`	Yes	API ID
`branch`	No	Git branch (for git-linked APIs)
`schemas`	Yes	Schema references
`collections`	Yes	Collection references
`releaseNotes`	No	Version release notes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits like permissions, side effects (e.g., whether it publishes immediately), or constraints. The description only states the action without such details.

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 a single, clear sentence with no redundant words. However, it could benefit from a bit more structure or detail to improve usefulness without becoming verbose.

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 tool's complexity (6 parameters, no output schema, no annotations), the description is too minimal. It lacks context about versioning semantics, required prerequisites, or relationship to other tools.

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%, so the description adds no parameter-level value beyond what the input schema already provides. Baseline 3 is appropriate as the description does not enhance understanding of how to use the parameters.

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 the verb 'Create' and resource 'new version of an API', which accurately distinguishes it from sibling tools like create_api (creates an API) or add_api_collection (adds collection to an API).

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?

No guidance is provided on when to use this tool versus alternatives such as create_api or update_api_version. The context implies its use for creating versions, but lacks explicit conditions 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