close_current_tab
Close the active browser tab and automatically switch to the previous one.
Instructions
Close the currently active tab and switch to the previous one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Close the active browser tab and automatically switch to the previous one.
Close the currently active tab and switch to the previous one.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions switching to the previous tab but does not disclose behavior for edge cases (e.g., only one tab, no previous tab). No annotations are provided, so the description carries the full burden and falls short.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, concise sentence that clearly conveys the action without unnecessary words. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no parameters and no output schema, the description is minimally adequate but lacks detail on edge cases or return behavior. More context about what happens when there is no previous tab would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so baseline 4 applies. The description adds no parameter-level information, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: close the active tab and switch to the previous one. It uses a specific verb and resource, and is easily distinguishable from sibling tools like 'close_browser' or 'open_new_tab'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. It does not mention edge cases like when only one tab is open, nor does it contrast with 'close_browser' or 'switch_to_window'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/seleniumboot/selenium-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server