page_go_backNavigate back to the previous page in browser history to return to a prior step in a web automation sequence or manual browsing.
Go back to the previous page in browser history
| Name | Required | Description | Default |
|---|---|---|---|
| tab_id | No | Optional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.8.8Input schema / descriptionPrevious value: -"Empty input schema for tools that don't require arguments."New value: +"Empty argument shape for a tab-scoped tool."Input schema / properties / tab_idAdded value: +{
+ "anyOf": [
+ {
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.",
+ "title": "Tab Id"
+}Input schema / titlePrevious value: -"EmptyInput"New value: +"TabScopedEmptyInput"Output schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": false,
- "properties": {
- "url": {
- "title": "Url",
- "type": "string"
- }
- },
- "required": [
- "url"
- ],
- "title": "PageGoBackData",
- "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_id": {
+ "description": "MCP tab id captured for this operation.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ },
+ "url": {
+ "title": "Url",
+ "type": "string"
+ }
+ },
+ "required": [
+ "url",
+ "tab_id"
+ ],
+ "title": "PageGoBackData",
+ "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.7.2v0.7.2v0.5.1Input schema / descriptionPrevious value: -"Empty input schema for tools that don't require parameters."New value: +"Empty input schema for tools that don't require arguments."v0.5.0Input schema / additionalPropertiesAdded value: +falseOutput schema / additionalPropertiesRemoved value: -falsev0.4.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say what happens when history is empty, whether the call blocks on load, or any side effects. With annotations present the bar is lower, but this adds no behavioral context at all.
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 front-loaded sentence with no filler, appropriate for a simple one-step navigation action. It is efficient rather than padded, though it is arguably too terse to earn a top score.
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?
An output schema exists, so return values need not be described, and annotations carry the safety traits. For a mutation-style navigation tool the remaining gap is edge-case behavior (no history available) and timing, which keeps it at minimum-viable 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?
Schema description coverage is 100% and the single optional tab_id parameter is fully documented in the schema, including the default-tab fallback behavior. Baseline 3 applies; the description contributes no additional parameter semantics.
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+resource ('go back to the previous page in browser history'), which clearly sets it apart from the sibling page_go_forward and page_navigate. It never names those siblings explicitly, but the directionality is unambiguous.
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?
There is no guidance on when to use this versus page_navigate, page_refresh, or page_go_forward, and no prerequisites or state conditions (e.g., whether history must exist). The agent must infer usage entirely from the one-line purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.