Skip to main content
Glama

shutdown_browser

Close the browser and end the WhatsApp automation session to stop background processes and free system resources.

Instructions

Close the browser context and stop the WhatsApp automation session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the shutdown logic, which calls self.stop().
    async def shutdown(self) -> dict[str, Any]:
        await self.stop()
        return {"stopped": True}
  • The MCP tool registration for 'shutdown_browser', which delegates to self.client.shutdown().
    "shutdown_browser": ToolDefinition(
        name="shutdown_browser",
        description="Close the browser context and stop the WhatsApp automation session.",
        input_schema={"type": "object", "properties": {}, "additionalProperties": False},
        handler=lambda _: self.client.shutdown(),
    ),
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the behavioral outcome (closing browser and stopping automation), which is appropriate for a destructive operation. However, it doesn't mention whether this is reversible, what happens to unsaved data, or authentication implications, leaving some behavioral gaps.

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, efficient sentence with zero waste. It's front-loaded with the core action and consequence, making it immediately clear what the tool does without unnecessary elaboration.

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?

For a destructive operation with no annotations and no output schema, the description provides the essential purpose but lacks details about side effects, confirmation requirements, or what happens after shutdown. Given the complexity of terminating an automation session, more context about consequences would be helpful.

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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and doesn't need to compensate for any schema gaps.

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 specific action ('Close the browser context and stop the WhatsApp automation session'), which includes both the immediate effect (closing browser) and broader consequence (stopping automation). It distinguishes from sibling tools like 'get_auth_status' or 'send_message' by being the only termination operation.

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

Usage Guidelines4/5

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

The description implies usage context (when ending an automation session), but doesn't explicitly state when to use this vs alternatives like 'wait_until_ready' or prerequisites. It's clear this should be used to terminate the session, but lacks explicit exclusions or comparison to other tools.

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/ekaksher/whatsapp-mcp'

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