Skip to main content
Glama
postmanlabs

Postman

Official
by postmanlabs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create an environment

createEnvironment

Create a new Postman environment in a specified workspace, defining variables, secret types, and enabling shared variable values.

Instructions

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.

  • Only shared variable values can be modified through the Postman API. A shared variable is an environment variable with its value synced and stored in the Postman cloud, and can be accessed by your teammates in the environment's workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesThe workspace's ID.
environmentNoInformation about the environment.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv2.12.0
    • removedInput schema / properties / environment / properties / values / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / environment / properties / values / items / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "description": "Information about the variable.",
+    "properties": {
+      "description": {
+        "description": "The variable's description.",
+        "maxLength": 512,
+        "type": "string"
+      },
+      "enabled": {
+        "description": "If true, the variable is enabled.",
+        "type": "boolean"
+      },
+      "key": {
+        "description": "The variable's name.",
+        "type": "string"
+      },
+      "type": {
+        "description": "The variable's type:\n- `secret` — The variable value is masked.\n- `default` — The variable value is visible in plain text.\n",
+        "enum": [
+          "secret",
+          "default"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "The variable's value.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Information about the variable stored in the Postman Vault. This property only returns when a variable is defined as secret.",
+    "properties": {
+      "description": {
+        "description": "The variable's description.",
+        "maxLength": 512,
+        "type": "string"
+      },
+      "enabled": {
+        "description": "If true, the variable is enabled.",
+        "type": "boolean"
+      },
+      "key": {
+        "description": "The variable's name.",
+        "type": "string"
+      },
+      "secret": {
+        "description": "If true, the variable is marked as secret and its value is retrieved from the mentioned provider in the source field.",
+        "type": "boolean"
+      },
+      "source": {
+        "additionalProperties": false,
+        "description": "Information about the source of the variable's value.",
+        "properties": {
+          "postman": {
+            "additionalProperties": false,
+            "description": "Information about the Postman-specific source of the variable's value.",
+            "properties": {
+              "secretId": {
+                "description": "The variable's secret ID.",
+                "type": "string"
+              },
+              "type": {
+                "const": "cloud",
+                "description": "The variable's type:\n- `cloud` — The variable value is synced and stored in the Postman Cloud.\n",
+                "type": "string"
+              },
+              "vaultId": {
+                "description": "The variable's ID in the Postman Vault.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "provider": {
+            "const": "postman",
+            "description": "The secret's provider.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": {
+        "description": "The variable's type:\n- `secret` — The variable value is masked.\n- `default` — The variable value is visible in plain text.\n",
+        "enum": [
+          "secret",
+          "default"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "The variable's value.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / environment / properties / values / items / description
      Removed value: -"Information about the environment's variables."
    • removedInput schema / properties / environment / properties / values / items / properties
      Removed value: -{
-  "description": {
-    "description": "The variable's description.",
-    "maxLength": 512,
-    "type": "string"
-  },
-  "enabled": {
-    "description": "If true, the variable is enabled.",
-    "type": "boolean"
-  },
-  "key": {
-    "description": "The variable's name.",
-    "type": "string"
-  },
-  "type": {
-    "description": "The variable's type:\n- `secret` — The variable value is masked.\n- `default` — The variable value is visible in plain text.\n",
-    "enum": [
-      "secret",
-      "default"
-    ],
-    "type": "string"
-  },
-  "value": {
-    "description": "The variable's value.",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / environment / properties / values / items / type
      Removed value: -"object"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: request body size limit (30MB), handling of 411 error, default workspace selection, and the limitation on modifying only shared variable values. These details help the agent understand side effects and constraints without contradicting the readOnlyHint=false annotation.

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 main description is concise, and the note is structured with bullet points. However, the note about shared variables is lengthy and could be trimmed, though it is relevant. Overall, it is not excessively verbose.

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?

The description covers operational details like size limits and error handling, but it does not mention the success return value or any prerequisites. The workspace parameter discrepancy (optional in description vs required in schema) leaves some ambiguity. Given the tool's complexity and lack of output schema, more detail on creation outcomes would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantics for the workspace parameter (defaults to oldest personal Internal workspace when omitted) and for the values parameter (only shared variable values can be modified via API). However, there is a contradiction: the schema marks workspace as required, while the description implies it is optional, which could confuse the agent.

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 starts with 'Creates an environment.' which clearly states a specific verb and resource. It distinguishes from sibling tools like createCollection and createWorkspace by specifically targeting environments.

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?

The description provides context about default workspace behavior and error handling, but does not explicitly state when to use this tool versus alternatives (e.g., updateEnvironment). There is no mention of exclusions or comparison with sibling create tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/postmanlabs/postman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server