Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Clear Web Storage

storage_clear
Destructive

Clears one key or all items from localStorage or sessionStorage in a specified browser tab, helping reset web state for automation and testing.

Instructions

Clear one key or all items from localStorage/sessionStorage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoOptional key. Empty clears the area.
areaNolocal
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.8
    • addedInput schema / properties / tab_id
      Added 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"
+}
    • changedOutput schema / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "data": {
-        "additionalProperties": false,
-        "properties": {
-          "area": {
-            "title": "Area",
-            "type": "string"
-          },
-          "cleared": {
-            "const": true,
-            "title": "Cleared",
-            "type": "boolean"
-          },
-          "key": {
-            "title": "Key",
-            "type": "string"
-          }
-        },
-        "required": [
-          "area",
-          "key",
-          "cleared"
-        ],
-        "title": "StorageClearData",
-        "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": {
+          "area": {
+            "title": "Area",
+            "type": "string"
+          },
+          "cleared": {
+            "const": true,
+            "title": "Cleared",
+            "type": "boolean"
+          },
+          "key": {
+            "title": "Key",
+            "type": "string"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "area",
+          "key",
+          "cleared",
+          "tab_id"
+        ],
+        "title": "StorageClearData",
+        "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"
+  }
+]
  2. Addedv0.7.2

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The destructive/safety profile is already fully covered by destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the bar is low. The description adds which storage areas are affected and the scope of clearing, but says nothing about irreversibility or tab targeting beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler that delivers scope and resource simultaneously.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, return values and safety need not be re-explained. The description is nearly complete, losing only a little for not clarifying tab-targeting behavior, which the schema handles.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: 'key' and 'tab_id' are documented in the schema, and 'area' carries an enum. The description's 'one key or all items' merely restates the schema's 'Empty clears the area' rather than adding new semantics, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Clear') plus the exact resource ('localStorage/sessionStorage') and scope ('one key or all items'). An agent can distinguish it immediately from storage_get and storage_set without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the clearing use case and the key-vs-all choice, but gives no explicit when-to-use guidance or pointers to adjacent siblings such as browser_cookies_clear or storage_set. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools