Skip to main content
Glama
Sign In
MCP-Insomnia

MCP-Insomnia

by anggasct
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_from_postman

Import a Postman Collection v2.1 JSON file to convert and manage it as an Insomnia-compatible API collection.

Instructions

Import collections from a Postman Collection v2.1 JSON file

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": {
      "filePath": "<filePath>"
    },
    "name": "import_from_postman"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesPath to the Postman collection JSON file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.2
  2. Removedv0.3.0
  3. First observedv0.4.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations exist, so the description alone must disclose behavior. It fails to mention whether importing overwrites existing collections, merges data, or requires specific permissions. The behavioral impact is unclear.

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, well-structured sentence that front-loads the action and resource. No redundant or unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one required parameter and no output schema, the description covers the core purpose and input format adequately. It could briefly mention the outcome (e.g., creates a collection) but remains largely sufficient.

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

Parameters5/5

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

The description adds value beyond the schema by specifying the exact format (Postman Collection v2.1 JSON) and indicates that the file must be a collection. Schema coverage is 100%, but the description enriches the semantic meaning.

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 'Import', the resource 'collections', and specifies the format 'Postman Collection v2.1 JSON file'. This distinguishes it from sibling tools like import_from_curl and import_from_openapi.

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 vs alternatives (e.g., import_from_openapi). There is no mention of prerequisites, success conditions, or when not to use it.

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