Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Web Storage

storage_set
Destructive

Set a single localStorage or sessionStorage key-value pair for a web page. The stored value is not echoed in the response.

Instructions

Set one localStorage/sessionStorage item. The value is not echoed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
areaNolocal
valueYesString value to store. Not echoed in result.
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"
-          },
-          "key": {
-            "title": "Key",
-            "type": "string"
-          },
-          "set": {
-            "const": true,
-            "title": "Set",
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "area",
-          "key",
-          "set"
-        ],
-        "title": "StorageSetData",
-        "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"
+          },
+          "key": {
+            "title": "Key",
+            "type": "string"
+          },
+          "set": {
+            "const": true,
+            "title": "Set",
+            "type": "boolean"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "area",
+          "key",
+          "set",
+          "tab_id"
+        ],
+        "title": "StorageSetData",
+        "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

A4/5.0
Behavior4/5

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

Annotations already cover the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false). The description adds a concrete behavioral detail beyond that: 'The value is not echoed', which tells the agent not to expect the written value back even though an output schema exists. It does not, however, disclose permission requirements or the effect on other storage keys.

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?

Two short sentences, front-loaded with the action and scope, followed by the one surprising behavioral fact. Nothing is wasted.

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?

The tool is simple (set one item), has an output schema (so return shape needn't be described), and annotations cover the safety profile. The description is nearly complete; the only gap is that 'area' and 'tab_id' semantics rely entirely on the schema.

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 50%, so the description must compensate for half the parameters, but it only mentions the key/value pair implicitly and says nothing about 'area' or 'tab_id'. The schema does describe tab_id and value, so baseline 3 is fair given partial coverage.

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 (Set) and resource (one localStorage/sessionStorage item), and distinguishes clearly from siblings storage_get and storage_clear by naming the exact scope 'one ... item'. An agent can immediately tell this is the write counterpart to storage_get.

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 when to use it via the 'set ... item' verb and the localStorage/sessionStorage framing, but it never explicitly says when to prefer this over e.g. storage_clear or browser_cookies_set, nor states prerequisites. 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