Loading ToolBench
A simple MCP server to operate on the Postman API
Server provides 10 tools with complete JSON schemas and descriptions. All tools follow verb_noun naming (create-*). Descriptions are present but vary in quality, some are verbose with external links (create-collection: 287 chars), others are concise (create-collection-fork: 89 chars). All tools declare input schemas with typed properties. However, parameter descriptions are often generic or missing context about constraints, dependencies, and error recovery. No output schemas documented. Error handling is minimal, no guidance on retryability, user-fixable vs fatal errors, or recovery steps. Tool annotations (destructiveHint) are present but underutilized. Composition is sound: each tool has one responsibility, and naming is consistent. Missing: pagination guidance, rate-limit handling, and per-parameter validation rules in descriptions.
Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** - If you do not include the `workspace` query parameter, the system creates the collection in the oldest personal Internal workspace you own. - For a complete list of available property values for this endpoint, use the following references available in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html): - `info` object — Refer to the **Information** entry. - `item` object — Refer to the **Items** entry. - For all other possible values, refer to the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
Creates a comment on a collection. To create a reply on an existing comment, include the `threadId` property in the request body. **Note:** This endpoint accepts a max of 10,000 characters.
Creates a folder in a collection. For a complete list of properties, refer to the **Folder** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). You can use this endpoint to to import requests and responses into a newly-created folder. To do this, include the `requests` field and the list of request objects in the request body. For more information, see the provided example. **Note:** It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a folder with a blank name.
Creates a [fork](https://learning.postman.com/docs/collaborating-in-postman/version-control/#creating-a-fork) from an existing collection into a workspace.
No output schemas documented. LLMs cannot predict response structure or plan downstream tool calls. Responses are inferred from API docs, not explicit tool definitions.
Parameter descriptions lack constraint details. E.g., 'workspace' is described as 'The workspace's ID' but does not specify format, length, or how to obtain it. LLMs cannot validate inputs before calling.
No error handling guidance. Tools do not document retryability, user-fixable errors, or recovery steps. E.g., if workspace ID is invalid, the LLM has no guidance on what to do next.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | <=2025-11-25 | v2 |
Creates a request in a collection. For a complete list of properties, refer to the **Request** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a request with a blank name.
Creates a request response in a collection. For a complete list of request body properties, refer to the **Response** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name.
Creates an environment. **Note:** - The request body size cannot exceed the maximum allowed size of 30MB. - If you receive an HTTP `411 Length Required` error response, manually pass the `Content-Length` header and its value in the request header. - If you do not include the `workspace` query parameter, the system creates the environment in the oldest personal Internal workspace you own.
Creates a comment on a folder. To create a reply on an existing comment, include the `threadId` property in the request body. **Note:** This endpoint accepts a max of 10,000 characters.
Creates a mock server in a collection. **Note:** - You cannot create mocks for collections added to an API definition. - If you do not include the `workspaceId` query parameter, the system creates the mock server in the oldest personal Internal workspace you own.
Creates a monitor. **Note:** - You cannot create monitors for collections added to an API definition. - If you do not pass the `workspace` query parameter, the system creates the monitor in the oldest personal Internal workspace you own.
Descriptions reference external documentation (Postman Collection Format v2.1.0 schema) but do not inline key constraints. LLMs cannot follow external links; they need self-contained descriptions.
No pagination or result-limiting guidance. Tools like create-monitor accept complex nested objects (distribution, notifications) but do not document max payload size or response truncation behavior.