tab_switchSwitch to a browser tab by its ID, making it the active tab for subsequent automation tasks.
Switch the active browser tab by id from tab_list.
| Name | Required | Description | Default |
|---|---|---|---|
| tab_id | Yes | MCP tab id from tab_list, or the underlying DrissionPage native tab id. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.8.0v0.7.2v0.7.2Output schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": false,
- "properties": {
- "tab": {
- "additionalProperties": false,
- "properties": {
- "active": {
- "type": "boolean"
- },
- "connected": {
- "type": "boolean"
- },
- "id": {
- "type": "string"
- },
- "native_id": {
- "type": "string"
- },
- "title": {
- "type": "string"
- },
- "url": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "native_id",
- "url",
- "title",
- "active",
- "connected"
- ],
- "title": "TabSummary",
- "type": "object"
- },
- "tab_id": {
- "type": "string"
- },
- "url": {
- "type": "string"
- }
- },
- "required": [
- "tab",
- "tab_id",
- "url"
- ],
- "title": "TabSwitchData",
- "type": "object"
- },
- "message": {
- "type": "string"
- },
- "ok": {
- "const": true
- }
- },
- "required": [
- "ok",
- "message",
- "data"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": true,
- "type": "object"
- },
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "type": "string"
- },
- "details": {
- "additionalProperties": true,
- "type": "object"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ],
- "type": "object"
- },
- "message": {
- "type": "string"
- },
- "ok": {
- "const": false
- }
- },
- "required": [
- "ok",
- "message",
- "error"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "tab": {
+ "additionalProperties": true,
+ "title": "Tab",
+ "type": "object"
+ },
+ "tab_id": {
+ "title": "Tab Id",
+ "type": "string"
+ },
+ "url": {
+ "title": "Url",
+ "type": "string"
+ }
+ },
+ "required": [
+ "tab",
+ "tab_id",
+ "url"
+ ],
+ "title": "TabSwitchData",
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ },
+ "ok": {
+ "const": true
+ }
+ },
+ "required": [
+ "ok",
+ "message",
+ "data"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "details": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ },
+ "ok": {
+ "const": false
+ }
+ },
+ "required": [
+ "ok",
+ "message",
+ "error"
+ ],
+ "type": "object"
+ }
+]v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=false and destructiveHint=true, indicating a state-changing operation. The description adds no additional behavioral context such as side effects on the previously active tab, session state, or prerequisites, so it provides little beyond the structured annotations.
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?
The description is a single concise sentence with the verb and object front-loaded. Every word contributes to the core action and id source; there is no redundancy or filler.
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?
Given the simple one-parameter tool and the presence of an output schema, this description is adequate. It names the action, resource, and id source; the only minor gap is not explicitly stating that tab_list should be called first to obtain a valid id, but that is already implied by the schema description.
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?
The input schema fully documents tab_id (100% coverage) as either an MCP tab id from tab_list or a DrissionPage native id. The description's 'by id from tab_list' only echoes this existing schema detail without adding new semantic meaning.
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 states a specific verb ('Switch') applied to a specific resource ('the active browser tab'), and it identifies the id source ('from tab_list'). This clearly distinguishes it from sibling tools like tab_close and tab_list, which have different purposes.
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?
The description implies the tool should be used when the agent has a tab_id from tab_list and wants to change the active tab. However, it does not explicitly state when to use it versus alternatives, nor does it provide exclusions (e.g., 'use tab_close to close a tab').
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/jumodada/Drissionpage-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server