E2B MCP Server

install_packages

Install Python pip or Node.js npm packages inside a secure sandbox environment. Specify language and package list to set up dependencies for code execution.

Instructions

Install packages in the sandbox environment (Python pip or Node.js npm)

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": {
      "packages": "<packages>",
      "language": "<language>"
    },
    "name": "install_packages"
  }
}

Input Schema

Name	Required	Description
`language`	Yes	Language ecosystem for package installation
`packages`	Yes	List of packages to install
`sandbox_id`	No	Optional sandbox ID to use specific sandbox

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that packages are installed via pip/npm, without mentioning side effects, persistence, failure behavior, or return values. This is a significant gap for a tool that mutates the sandbox environment.

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 sentence that front-loads the verb and resource, then adds the ecosystem detail efficiently. There is zero filler and no redundant repetition of schema information.

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?

The core call can be constructed from schema plus description, but with no annotations and no output schema, an agent is left guessing about return values, failure handling, and when to prefer this over the execute_* siblings. This is minimal but not entirely inadequate for a straightforward install operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by mapping the language enum to actual package managers (pip for Python, npm for Node.js) and clarifying that installation targets the sandbox, which helps the agent interpret the parameters correctly.

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?

Clearly states a specific action (install packages), a target resource (sandbox environment), and the two ecosystems involved (Python pip or Node.js npm). This distinguishes it from sibling tools like execute_python/execute_javascript and file operations.

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 implies when to use it (when dependencies are needed in the sandbox) but does not explicitly compare it to alternatives like execute_python/execute_javascript or mention when not to use it. The usage context is left to inference.

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

Deploy Server