Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Browser Permission

browser_permission_set
DestructiveIdempotent

Set one Chromium site permission, such as camera, microphone, or geolocation, to granted, denied, or prompt for an exact HTTP(S) origin.

Instructions

Set one permission to granted, denied, or prompt for one bounded origin in the current Chromium context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originNoExact HTTP(S) origin. Defaults to the current page origin.
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.
settingYes
permissionYes

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": {
-          "applied": {
-            "const": true,
-            "title": "Applied",
-            "type": "boolean"
-          },
-          "context_scope": {
-            "const": "current_browser_context",
-            "title": "Context Scope",
-            "type": "string"
-          },
-          "observed_state": {
-            "anyOf": [
-              {
-                "enum": [
-                  "granted",
-                  "denied",
-                  "prompt",
-                  "unsupported"
-                ],
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ],
-            "title": "Observed State"
-          },
-          "origin": {
-            "title": "Origin",
-            "type": "string"
-          },
-          "permission": {
-            "title": "Permission",
-            "type": "string"
-          },
-          "setting": {
-            "enum": [
-              "granted",
-              "denied",
-              "prompt"
-            ],
-            "title": "Setting",
-            "type": "string"
-          },
-          "verified": {
-            "title": "Verified",
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "permission",
-          "setting",
-          "origin",
-          "applied",
-          "verified",
-          "observed_state",
-          "context_scope"
-        ],
-        "title": "BrowserPermissionSetData",
-        "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": {
+          "applied": {
+            "const": true,
+            "title": "Applied",
+            "type": "boolean"
+          },
+          "context_scope": {
+            "const": "current_browser_context",
+            "title": "Context Scope",
+            "type": "string"
+          },
+          "observed_state": {
+            "anyOf": [
+              {
+                "enum": [
+                  "granted",
+                  "denied",
+                  "prompt",
+                  "unsupported"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "title": "Observed State"
+          },
+          "origin": {
+            "title": "Origin",
+            "type": "string"
+          },
+          "permission": {
+            "title": "Permission",
+            "type": "string"
+          },
+          "setting": {
+            "enum": [
+              "granted",
+              "denied",
+              "prompt"
+            ],
+            "title": "Setting",
+            "type": "string"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          },
+          "verified": {
+            "title": "Verified",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "permission",
+          "setting",
+          "origin",
+          "applied",
+          "verified",
+          "observed_state",
+          "context_scope",
+          "tab_id"
+        ],
+        "title": "BrowserPermissionSetData",
+        "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.8.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, and the description does not contradict them. It adds the useful scoping detail that only ONE permission and ONE origin are affected, which bounds the destructive blast radius, but it does not disclose reversibility, whether the change is persisted, or interaction with existing permissions. With rich annotation coverage, a 3 is appropriate.

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 tight sentence with the verb, value enumeration, scope, and context front-loaded. No waste.

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?

Output schema exists, so return values need not be explained. The description covers the action, its bounded scope, and target values. It lacks explicit when-to-use guidance against siblings and does not note prerequisites such as needing a page/context to exist, but is otherwise sufficient for a state-mutating permission tool.

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%; origin and tab_id are documented in the schema but setting and permission enums have no descriptions. The description names the three setting values, partially compensating, but adds no semantics for tab_id or how origin interacts with the current context beyond what the schema states. Baseline 3 for moderate 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), resource (one permission), and enumerates the exact target values (granted/denied/prompt) and scope (one bounded origin, current Chromium context). An agent can immediately distinguish this from browser_permission_get, browser_permissions_reset, and browser_headers_set.

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 usage via scope ('one bounded origin in the current Chromium context'), but never states when to use this versus sibling tools like browser_permissions_reset or browser_permission_get, nor does it explain when to specify an origin versus rely on the default. Usage is implied rather than instructed.

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