browser_new_page
Create a new browser page for web automation. Use it to open a fresh tab and start interacting with websites via Playwright.
Instructions
创建新页面
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Create a new browser page for web automation. Use it to open a fresh tab and start interacting with websites via Playwright.
创建新页面
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description carries no behavioral information. It does not disclose whether this creates a new tab, a new browser context, whether it returns a page reference, or whether it navigates to a default URL. The agent is left completely uninformed about side effects or required state.
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 this is under-specification rather than effective conciseness. It contains only a single phrase with no additional context, structure, or details, offering minimal value to an AI agent.
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?
Given the tool's likely side effects (creating a new page) and the absence of any output schema or annotations, the description is completely inadequate. It does not explain what constitutes a 'page', what state the browser must be in, what the tool returns, or how it interacts with other browser tools.
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?
The tool has zero parameters, and the input schema is empty. With schema coverage trivially 100% and no parameters to describe, the baseline score is 4. The description adds no additional parameter context, but none is needed.
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 '创建新页面' directly translates to 'create new page', which is essentially a restatement of the tool name 'browser_new_page'. While it adds a verb, it fails to specify what kind of page is created, whether it opens a blank tab, a new window, or triggers a navigation. It does not distinguish this tool from browser_goto or browser_launch beyond the name.
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 provides no guidance on when to use this tool versus alternatives like browser_goto or browser_switch_page. There is no mention of typical scenarios, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/91fapiao-cn/playwright-browser-skill'
If you have feedback or need assistance with the MCP directory API, please join our Discord server