Skip to main content
Glama
roxybrowserlabs

RoxyBrowser MCP Server

Official

roxy_close_browsers

Close browser instances by providing their directory IDs. Useful for batch termination to free resources during automation.

Instructions

Close multiple browsers by their directory IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dirIdsYesArray of browser directory IDs to close
Behavior2/5

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

Without annotations, the description fails to disclose behavioral traits such as irreversibility, side effects (e.g., data loss), or whether browsers can be reopened. It only states the action.

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?

Exceptionally concise one-sentence description, front-loaded with action and resource, no unnecessary words.

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?

Adequate for a simple close operation with one parameter, but lacks behavioral context (output, errors) and assumes common understanding of 'close' in this domain.

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%, so the schema already describes the parameter. The description adds minimal value beyond 'by their directory IDs', which is already in the parameter description.

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 verb 'Close' and resource 'multiple browsers', and specifies the method 'by their directory IDs', effectively distinguishing it from sibling tools like roxy_open_browsers.

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?

No guidance on when to use this tool versus alternatives (e.g., roxy_delete_browsers), no prerequisites or when-not-to-use information provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roxybrowserlabs/roxybrowser-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server