Skip to main content
Glama
Sign In
MCP-Insomnia

MCP-Insomnia

by anggasct
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sync_from_insomnia

Import an Insomnia workspace into MCP storage to manage and execute API collections.

Instructions

Import a collection from Insomnia app into MCP storage

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "sync_from_insomnia"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesInsomnia workspace ID to import

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only says 'import', which implies creation but gives no details on side effects, idempotency, or required authentication. The agent cannot infer if existing MCP collections are overwritten or if workspace deletion is possible.

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?

A single, efficient sentence with no superfluous words. It directly communicates the core action and target.

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 simplicity, the description lacks important context such as how the import behaves (additive vs. overwrite), whether it requires a live Insomnia connection, and what output or confirmation the agent can expect. This is insufficient for safe autonomous invocation.

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?

The schema provides 100% coverage with a description for the workspaceId parameter. The tool description adds context about the source (Insomnia app) and destination (MCP storage), which reinforces the parameter's meaning but does not significantly extend it.

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 clearly states it imports a collection from Insomnia app into MCP storage, with a specific verb and resource. It distinguishes from sibling import tools like import_from_curl because it targets Insomnia specifically, though it could be more precise about 'collection' vs 'workspace'.

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?

The description provides no guidance on when to use this tool versus alternatives like import_from_insomnia_export or sync_all_from_insomnia. There is no mention of prerequisites, context, or exclusions.

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