Get the URL of a specific browser page using its page ID or session ID, enabling verification of page states during browser automation.
Page URL.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | No | Stable page ID; defaults to the session active page | |
| sessionId | No | Optional session ID; defaults to this MCP client active session |
Changes observed during successful MCP inspections.
v2026.8.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, covering the safety profile, but the description adds no further behavioral context. It does not disclose return format, error behavior, or how the URL is resolved, though it does not contradict the annotation.
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?
The description is extremely short but under-specified, providing no actionable insight. Over-brevity at the expense of clarity is not effective conciseness.
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?
With no output schema and no meaningful description, the agent cannot determine what the tool returns (likely a URL string, but not stated) or how it fits among 50+ sibling tools. It is minimally viable at best.
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 coverage is 100% with clear descriptions for both pageId and sessionId, so the description is not required to explain parameters. It adds no extra meaning, but the schema handles the burden.
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?
The description 'Page URL.' is essentially a restatement of the tool name, lacking a verb and any indication of what action it performs or what it returns. It does not distinguish from sibling tools like nex_browser_page_title or nex_browser_connection_info.
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 description gives no guidance on when to use this tool vs alternatives, no mention of the default pageId/sessionId behavior, and no comparison with similar page-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.