Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Wait for URL

wait_for_url
Read-onlyIdempotent

Pause browser automation until the current tab's URL contains a specified substring or pattern, with optional timeout and tab targeting.

Instructions

Wait for the current URL to contain a substring

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.
timeoutNoTimeout in seconds
url_patternYesSubstring or pattern expected in the current URL

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": {
-          "matched": {
-            "const": true,
-            "title": "Matched",
-            "type": "boolean"
-          },
-          "timeout": {
-            "title": "Timeout",
-            "type": "number"
-          },
-          "url": {
-            "title": "Url",
-            "type": "string"
-          },
-          "url_pattern": {
-            "title": "Url Pattern",
-            "type": "string"
-          }
-        },
-        "required": [
-          "url_pattern",
-          "matched",
-          "url",
-          "timeout"
-        ],
-        "title": "WaitForUrlData",
-        "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": {
+          "matched": {
+            "const": true,
+            "title": "Matched",
+            "type": "boolean"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          },
+          "timeout": {
+            "title": "Timeout",
+            "type": "number"
+          },
+          "url": {
+            "title": "Url",
+            "type": "string"
+          },
+          "url_pattern": {
+            "title": "Url Pattern",
+            "type": "string"
+          }
+        },
+        "required": [
+          "url_pattern",
+          "matched",
+          "url",
+          "timeout",
+          "tab_id"
+        ],
+        "title": "WaitForUrlData",
+        "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. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / timeout / type
      Previous value: -"integer"New value: +"number"
  3. Addedv0.7.2
  4. Removedv0.7.2
  5. Changed2 schema fields changedv0.5.1
    • addedInput schema / properties / timeout / maximum
      Added value: +120
    • addedInput schema / properties / timeout / minimum
      Added value: +0
  6. Changed2 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / additionalProperties
      Removed value: -false
  7. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the scoping detail that it watches the current URL, but says nothing about what happens on timeout (error vs. false) or whether it blocks, which is the key behavioral question for a wait tool.

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

Conciseness4/5

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

A single efficient sentence with the core action front-loaded and no filler. It is perhaps too terse to be genuinely helpful, but nothing is wasted.

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

Completeness3/5

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, and annotations cover the safety profile. However, for a wait operation the description omits the timeout/failure outcome and any distinction from sibling wait tools, leaving gaps an agent must guess at.

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 description coverage is 100%, so tab_id, timeout, and url_pattern are all documented in the schema itself. The description adds no format or syntax detail for url_pattern beyond what the schema provides, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb (wait), resource (current URL), and condition (contain a substring), so the operation is unambiguous. It does not distinguish itself from siblings like wait_for_element, wait_until, or wait_time, which all involve waiting, leaving the agent to infer the difference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. With wait_until and wait_for_element in the sibling set, the agent gets no signal on which waiting primitive applies to URL-change scenarios versus element or generic conditions.

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