MCP-Insomnia

get_environment_variables

Retrieve environment variables from an Insomnia collection. Specify a collection ID to list variables, or include an environment ID to filter specific ones.

Instructions

Get environment variables from a collection

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

Input Schema

Name	Required	Description	Default
`collectionId`	Yes	ID collection
`environmentId`	No	Specific environment ID (optional)

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, the description carries the full burden of behavioral disclosure. It only states 'Get', implying a read-only operation, but fails to mention what happens if environmentId is omitted, whether it returns all variables, or any side effects. No details on authorization or rate limits.

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 that is front-loaded and directly reflects the tool's purpose. No unnecessary words or redundancy. For a simple 2-parameter tool, this is appropriately concise.

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 the lack of output schema and annotations, the description is somewhat incomplete. It does not explain the behavior when environmentId is omitted (e.g., returns all variables in collection?) or what the response format looks like. However, for a simple 'get' tool, it covers the basics.

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 input schema has 100% description coverage, with descriptions for both parameters ('ID collection', 'Specific environment ID (optional)'). The tool description does not add additional meaning or clarify usage beyond the schema. Baseline score is appropriate.

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 'Get environment variables from a collection' clearly states the action (Get) and the resource (environment variables from a collection). It distinguishes itself from siblings like 'set_environment_variable' which is a write operation. However, it does not explicitly differentiate from other read tools like 'get_collection_detail'.

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, such as when to use `get_environment_variables` vs `set_environment_variable` or other read tools. No prerequisites or context for use are given.

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