Skip to main content
Glama
Sign In
postman-mcp-server

postman-mcp-server

by delano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pull_environment

Pulls changes from a parent environment into a forked environment to keep them in sync.

Instructions

Pull changes from parent environment into forked environment

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": {
      "environmentId": "<environmentId>",
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "pull_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource (parent) environment ID in format: {ownerId}-{environmentId}
destinationYesDestination (fork) environment ID in format: {ownerId}-{environmentId}
environmentIdYesEnvironment ID in format: {ownerId}-{environmentId}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'pull changes' without disclosing side effects (e.g., overwriting, conflict handling, destructive behavior). Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that conveys the core function without any fluff. Perfectly concise and front-loaded.

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 lack of output schema and annotations, the description is too sparse. It does not cover return value, idempotency, or what happens when there are no changes. Incomplete for a 3-parameter tool with sibling ambiguity.

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 baseline is 3. The description does not add meaning beyond the schema's parameter descriptions (e.g., why three IDs are needed or how they relate). No extra value.

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 specific action (pull changes) and the resource (environment from parent to fork). It distinguishes from sibling tools like merge_environment_fork and fork_environment by implying a one-way sync.

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

Usage Guidelines2/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 like merge_environment_fork. The agent lacks context to decide between pulling and merging.

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

Deploy Server

Other Tools