MCP-Insomnia

sync_to_insomnia

Export a collection from MCP storage to Insomnia. Preview changes with dry-run or create a timestamped backup before applying the sync.

Instructions

Export a collection from MCP storage to Insomnia app

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": "sync_to_insomnia"
  }
}

Input Schema

Name	Required	Description
`backup`	No	When true, write an atomic timestamped backup of the Insomnia documents that would be overwritten before applying the sync. Backup failure aborts the sync.
`dryRun`	No	When true, return the planned diff and backup plan without writing to Insomnia or creating a backup file.
`projectId`	No	Insomnia project ID (optional, defaults to first project)
`collectionId`	Yes	MCP collection ID to export

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.0Sep 15, 2026

addedInput schema / properties / backup

Added value: +{
+  "description": "When true, write an atomic timestamped backup of the Insomnia documents that would be overwritten before applying the sync. Backup failure aborts the sync.",
+  "type": "boolean"
+}

addedInput schema / properties / dryRun

Added value: +{
+  "description": "When true, return the planned diff and backup plan without writing to Insomnia or creating a backup file.",
+  "type": "boolean"
+}

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

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure, but it only says 'Export' without noting that the operation can overwrite Insomnia documents. The backup parameter implies destructive overwrites, but the tool description itself does not disclose this or any other behavior such as failure modes or irreversibility.

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 front-loaded sentence with no filler or repetition. It is concise and easy to parse, though it sacrifices behavioral and contextual detail for brevity.

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?

For a mutating sync operation with no annotations and no output schema, the description is incomplete. It does not mention that the sync may overwrite existing Insomnia documents, that a preview tool exists, or that dryRun can be used to avoid writes. An agent cannot safely choose and invoke this tool based solely on the provided description.

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 description coverage is 100%, so the structured schema already documents all four parameters. The description adds no parameter-level meaning, but the baseline of 3 applies because the schema fully compensates for parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Export a collection from MCP storage to Insomnia app'. It clearly identifies direction and destination, which helps distinguish it from sync_from_insomnia and import tools. However, it does not explicitly differentiate itself from preview_sync_to_insomnia or export_collection.

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 given about when to use this tool versus alternatives. It does not mention preview_sync_to_insomnia for safe dry-run checking, sync_from_insomnia for the reverse direction, or when to prefer export_collection. Usage is only implied by the verb 'export'.

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