Skip to main content
Glama
Sign In
MCP-Insomnia

MCP-Insomnia

by anggasct
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

execute_insomnia_request

Run API requests from Insomnia directly with environment variable substitution, eliminating the need to sync.

Instructions

Execute a request directly from Insomnia app without syncing. Supports environment variable substitution.

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": {
      "requestId": "<requestId>"
    },
    "name": "execute_insomnia_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesRequest ID from Insomnia (starts with req_)
timeoutMsNoOptional request timeout in milliseconds. Default 30000. Set <= 0 for no timeout (MCP cancellation still applies).
environmentIdNoOptional environment ID to use for variable substitution
overrideVariablesNoOptional variables to override environment values (e.g., {"token": "abc123"})

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / timeoutMs
      Added value: +{
+  "description": "Optional request timeout in milliseconds. Default 30000. Set <= 0 for no timeout (MCP cancellation still applies).",
+  "type": "number"
+}
  2. Addedv0.5.2
  3. Removedv0.3.0
  4. First observedv0.4.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions no syncing and env var support, but omits important traits like whether the request is executed locally, whether it modifies state, error behavior, or permission requirements. This is insufficient for a tool that can execute potentially destructive actions.

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?

Two sentences that convey the core purpose and key behavior without extraneous words. Highly efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 fully described parameters, no output schema, and no annotations, the description covers the main functionality but misses details about timeout behavior, return value, error handling, and cancellation. The description is adequate but not comprehensive.

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 each parameter described. The description adds 'Supports environment variable substitution' which aligns with environmentId and overrideVariables, but does not enhance understanding beyond the schema. Baseline 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 ('Execute a request') and the resource ('from Insomnia app'), and distinguishes from sibling tools like 'sync_to_insomnia' by specifying 'without syncing'. It also mentions support for environment variable substitution, which is a key differentiator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at when not to use it (when syncing is needed) but does not provide explicit alternatives or when-to-use guidance. It lacks explanation of prerequisites or comparison with siblings like 'execute_request' or 'sync_all_from_insomnia'.

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