Skip to main content
Glama
Sign In
MCP-Insomnia

MCP-Insomnia

by anggasct
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_from_insomnia_export

Import API collections from an Insomnia V4 export file to migrate or restore them in your workspace.

Instructions

Import collections from a standard Insomnia V4 export 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_insomnia_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesThe absolute path to the Insomnia export file

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as error handling, whether existing collections are overwritten, or permissions required. The description carries the full burden but is minimal.

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 description is a single concise sentence, front-loaded with the core action. However, it is too brief to provide comprehensive guidance.

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?

While the tool is simple, the description lacks information on what happens after import (e.g., collection created, any conflicts), leaving the agent unaware of potential side effects.

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% with a single parameter filePath. The description adds no extra meaning beyond the schema's own description, so a baseline of 3 is appropriate.

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' and the resource 'collections from a standard Insomnia V4 export file', which is specific and distinguishes it from sibling tools like import_from_curl or import_from_postman.

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 (e.g., import_from_curl, import_from_openapi), nor are there any prerequisites or context about the import process.

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