page_refreshReload the current browser tab to fetch updated content or recover from stale page state. Optionally target a specific tab by id; otherwise the active tab is used.
Refresh the current page
| 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": "PageRefreshData",
- "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": "PageRefreshData",
+ "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 readOnlyHint=false, so the safety profile is known. The description adds nothing on top of that — it does not warn that a refresh discards unsaved form state, may re-submit a POST, or otherwise differ from a navigation. No contradiction, but no added value.
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 short sentence with no filler, so nothing is wasted and the verb is front-loaded. However, brevity here comes from under-specification rather than disciplined editing, so it earns no more than a middling 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 explained, but for a destructive, non-idempotent browser action the description should at least note the side effects of reloading and the tab-targeting behavior. As written, the definition leaves an agent with only the annotations to go on.
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 coverage is 100% and tab_id is well documented in the schema, so the baseline is 3. The description's phrase "current page" adds no meaning beyond the schema and slightly understates the tool, since tab_id can target a non-current tab.
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?
"Refresh the current page" restates the tool name and title almost verbatim; it names a verb and resource but adds no distinguishing detail. Among ~60 siblings there is nothing here to separate it from page_navigate, page_go_back, or wait_for_url beyond the obvious word 'refresh'.
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 when-to-use, when-not-to-use, or alternative guidance is provided. An agent must infer on its own that page_navigate is for loading a new URL and this tool is for reloading the existing one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.