MCP-Insomnia

import_from_curl

Convert a cURL command into a reusable API request and add it to an Insomnia collection, with optional folder and custom name.

Instructions

Create a request from a cURL command

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

Input Schema

Name	Required	Description
`folderId`	No	Optional folder ID to place the request in
`curlCommand`	Yes	The cURL command to parse
`requestName`	No	Name for the new request
`collectionId`	Yes	ID of the collection to add the request to

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.1/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Create' (a write operation) but does not describe side effects (e.g., changes to the collection), required permissions, error behavior, or the outcome (e.g., the created request model).

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—efficient and to the point. However, it is almost too sparse, lacking any secondary sentences that could provide valuable context without harming conciseness.

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 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what happens after creation (e.g., returns the new request), how errors are handled (e.g., invalid cURL), or any operational constraints (e.g., collection must exist). The agent has to rely entirely on the schema and assumptions.

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 baseline is 3. The description does not add any additional meaning beyond what the schema already provides; it merely restates the tool's purpose without elaborating on parameter usage, such as how the cURL command is parsed or the role of optional parameters like folderId.

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 'Create a request from a cURL command' is specific about the verb (create) and resource (request from cURL command). It clearly distinguishes this tool from sibling import tools like import_from_openapi and import_from_postman, which handle different formats.

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. It does not mention that this is specifically for cURL commands, nor does it state any prerequisites or scenarios where this tool is not appropriate.

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