Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Close Page

close_page

Closes a browser tab by referencing its unique page_id, which you obtain by listing open pages first.

Instructions

Close a browser tab. Use list_pages first to get the page_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>"
    },
    "name": "close_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.6.4

TDQS

A3.9/5.0
Behavior3/5

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

The description conveys the basic destructive action but does not disclose details like whether unsaved state is lost or if confirmation is needed. Without annotations, more detail would be beneficial.

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?

The description is extremely concise with two clear sentences, no fluff, and gets straight to the point.

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?

Given the tool's simplicity (one required param, no output schema), the description adequately covers the action and prerequisite. Could mention expected behavior or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not directly explain the page_id parameter beyond implying it comes from list_pages. With 0% schema description coverage, it adds minimal semantic value.

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?

The description clearly states the verb 'close' and resource 'browser tab', making the tool's purpose distinct from sibling tools like click or navigate.

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

Usage Guidelines4/5

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

Provides explicit prerequisite guidance: 'Use list_pages first to get the page_id.' This helps the agent know how to obtain the required input.

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