browser_cache_clearClear the HTTP cache for the current or specified browser tab while preserving cookies and Web Storage.
Clear HTTP cache without clearing cookies or Web Storage.
| 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": {
- "cleared": {
- "const": true,
- "title": "Cleared",
- "type": "boolean"
- }
- },
- "required": [
- "cleared"
- ],
- "title": "BrowserCacheClearData",
- "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": {
+ "cleared": {
+ "const": true,
+ "title": "Cleared",
+ "type": "boolean"
+ },
+ "tab_id": {
+ "description": "MCP tab id captured for this operation.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "required": [
+ "cleared",
+ "tab_id"
+ ],
+ "title": "BrowserCacheClearData",
+ "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.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the genuinely useful blast-radius detail that cookies and Web Storage survive, which the annotations cannot express.
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 sentence with zero filler; the verb and the scope exclusion are both front-loaded.
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 one-parameter, annotated tool with an output schema, the description covers the essential scope question. The omission of tab-scoped behavior (that clearing applies to the resolved tab) is a minor gap it could have closed.
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 tab_id parameter is fully documented in the schema, including the fallback to the current tab. The description adds nothing about tab scoping, so baseline 3 applies.
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?
States a specific verb (clear) and resource (HTTP cache), and immediately delimits scope by naming what is NOT cleared. This cleanly separates it from sibling tools browser_cookies_clear and storage_clear.
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 negative scoping ('without clearing cookies or Web Storage') implicitly tells the agent to use this tool when the goal is cache-only eviction and to use the cookie/storage siblings otherwise. There is no explicit when-to-use trigger or prerequisite statement, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.