Skip to content

v2.8.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Mar 11:47
v2.8.4
a73419b

New Features

MCP Instructions Resource

Added a built-in Instructions resource (postman://instructions) that provides MCP clients with comprehensive context about Postman concepts and a structured workflow for API discovery.

  • Covers all core Postman elements: workspaces, collections, environments, APIs, mocks, monitors, and tags
  • Includes a decision framework for choosing between Private and Public API Network searches
  • Provides step-by-step guidance for navigating collections after discovery
  • Server instructions now encourage MCP clients to read this resource before answering API-related questions

Improvements

Collection Creation Validation

Added a minLength constraint to the collection name field in createCollection, preventing the creation of collections with empty names.

Code Generation Parameter Resolution

Made the parametersResolution field required in generateCollection with a default value of "Example". The "Schema" strategy is no longer supported by the Postman API and will return an error.

Case-Insensitive Enum Handling

Updated the code generator to normalize uppercase-only enum values case-insensitively. LLM agents frequently submit lowercase values (e.g., "yaml" instead of "YAML", "openapi:3.1" instead of "OPENAPI:3.1"), which previously caused validation failures.

  • Affected tools: createSpec, generateSpecFromCollection, updateSpecFile, createCollectionRequest, updateCollectionRequest, and related response tools

Enterprise Plan Notice for Tags

Added a prominent Enterprise plan requirement notice to the getTaggedEntities tool description, so LLM agents understand that a 404 response on Free, Basic, or Professional plans is a plan restriction, not a broken tool.

Improved patchCollection Guidance

Added LLM-facing guidance to patchCollection warning against parallel calls on the same collection and clarifying which collection.variable fields to include.

Bug Fixes & Dependencies

  • Fixed patchCollection silently injecting disabled: false into every collection.variable item due to Zod .default() behavior, causing "invalid parameters" API errors. PATCH operations now use .optional() instead of .default() so omitted fields stay absent in the request body.

Full Changelog: v2.8.2...v2.8.4

Assets 5
Loading