MCP-Insomnia

export_collection

Export an Insomnia API collection to JSON (V4 format). Provide the collection ID to convert it into a portable file, with an optional output path.

Instructions

Export collection to JSON (Insomnia V4 format)

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": {
      "collectionId": "<collectionId>"
    },
    "name": "export_collection"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	No	Output file path (optional)
`collectionId`	Yes	ID of the collection to export

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.2May 15, 2026
Removedv0.3.0May 1, 2026
First observedv0.4.0Jan 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations provided, so description must cover behavioral traits. The description implies a read operation (export), but does not explicitly state that it is non-destructive or disclose side effects (e.g., file creation behavior). It adds the format detail but lacks clarity on safety.

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, concise sentence with no superfluous words. It effectively front-loads the key information: action, resource, and format.

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?

Despite the tool's relative simplicity, the description misses critical context: no return value description (especially since no output schema), no error handling hints, and no mention of behavior when collectionId is invalid or filePath is omitted. The format is specified, but overall completeness is low.

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 parameters are already well-documented in the schema. The description adds the output format context ('Insomnia V4'), but does not elaborate on parameter usage beyond what the schema provides. 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 action ('Export'), the resource ('collection'), and the output format ('JSON (Insomnia V4 format)'). It distinguishes well from sibling tools like import and sync tools.

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 on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or when not to use it. With several sync and import tools in the sibling list, contextual guidance is missing.

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