Get the current page title from an active browser session or specific page in NexBrowser. Use it to verify page identity or confirm navigation results during automation.
Page title.
| 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?
The annotation readOnlyHint=true already signals a safe read operation, but the description adds no behavioral context. It does not disclose what is returned, whether the page must be loaded, or any potential failure modes.
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?
At two words, the description is under-specified rather than concise. It fails to convey necessary information and does not earn its place as a helpful tool description.
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?
For a simple getter, the lack of an output schema and the absence of any explanation about the return value or behavioral constraints make the description incomplete. A minimal phrase like 'Gets the title of the specified page' would be needed.
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 description coverage is 100%, with both parameters (pageId, sessionId) clearly described in the input schema. The description itself adds no parameter information, but the schema carries the full burden, warranting the baseline score of 3.
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 title." is a noun phrase that essentially restates the tool name without a verb or action. It does not clearly state that it retrieves the page title, nor does it distinguish from siblings like nex_browser_get_text or nex_browser_page_url.
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?
No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer the tool's purpose purely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.