Skip to main content
Glama

browser.create_session

Launch a new browser session with optional start URL, proxy settings, authentication profiles, and custom user agents for automated web interactions.

Instructions

Create a new browser session and optionally navigate to a start URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
start_urlNo
storage_state_pathNo
auth_profileNo
proxy_serverNo
proxy_usernameNo
proxy_passwordNo
user_agentNo
totp_secretNo

Implementation Reference

  • The _create_session method in McpToolGateway is the handler implementation for the "browser.create_session" MCP tool. It delegates the logic to the manager's create_session method.
    async def _create_session(self, payload: CreateSessionRequest) -> dict[str, Any]:
        return await self.manager.create_session(
            name=payload.name,
            start_url=payload.start_url,
            storage_state_path=payload.storage_state_path,
            auth_profile=payload.auth_profile,
            request_proxy_server=payload.proxy_server,
            request_proxy_username=payload.proxy_username,
            request_proxy_password=payload.proxy_password,
            user_agent=payload.user_agent,
            totp_secret=payload.totp_secret,
        )
  • Tool registration for "browser.create_session" within the McpToolGateway class.
    ToolSpec(
        name="browser.create_session",
        description="Create a new browser session and optionally navigate to a start URL.",
        input_model=CreateSessionRequest,
        handler=self._create_session,
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions that optional navigation occurs, but fails to explain session persistence, isolation guarantees, resource limits, or what the tool returns (e.g., session ID).

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 consists of a single efficient sentence with no redundant words. It is appropriately front-loaded with the primary action.

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 the high complexity (9 configuration parameters covering authentication, proxy, storage state, and TOTP) and lack of output schema or annotations, the description is severely incomplete. It covers only the basic creation action while omitting critical configuration context.

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

Parameters2/5

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

Schema description coverage is 0%, leaving all 9 parameters undocumented in the structured schema. The description implicitly references 'start_url' but provides no semantic information for the other 8 parameters including 'auth_profile', 'proxy_server', or 'totp_secret', failing to compensate for the schema gap.

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 clearly states the core action ('Create a new browser session') and mentions the optional navigation feature. However, it does not distinguish this from the sibling tool 'fork_session', which also creates sessions but likely from existing state.

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 is provided on when to use this tool versus alternatives like 'fork_session', or when to use specific parameters like 'storage_state_path' versus 'auth_profile'. No prerequisites or error conditions are mentioned.

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/LvcidPsyche/auto-browser'

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