Skip to main content
Glama
Sign In
Chrome Browser Control

Chrome Browser Control

by vKongv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Page status

page_status

Get current page status, viewport/scroll state, and resource counts for a chosen Chrome tab.

Instructions

Return lightweight page status, viewport/scroll state, and resource summary counts for an allowed target tab.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "page_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoOptional Chrome tab id. Defaults to the claimed session tab, then the active tab.
documentIdNoExact frame document id returned by list_frames. Omit to target the current top document.
sessionTabIdNoOptional claimed tab session id returned by claim_tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry all behavioral disclosure. It mentions 'lightweight' and 'allowed target tab' but does not clarify permission requirements, whether the operation is read-only, failure modes, or any side effects. The brevity leaves significant behavioral uncertainty.

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?

The description is a single sentence that front-loads the primary purpose and then lists the returned elements. It is concise and free of fluff, though it could arguably include a bit more contextual detail without losing efficiency.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and an output schema, the description is incomplete for an agent to confidently call the tool. It does not explain the return format, prerequisites like claiming a tab, or error conditions, leaving important operational details unspecified.

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 coverage is 100% and each parameter (tabId, documentId, sessionTabId) has a descriptive string in the schema. The tool description adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 action ('Return lightweight page status') and names the specific data included (viewport/scroll state, resource summary counts) for an allowed target tab. This is clear and distinguishes it from general snapshot tools, though it doesn't explicitly contrast with browser_status.

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 guidance on when to use this tool versus siblings like browser_status or snapshot. It does not mention prerequisites (e.g., needing a claimed tab) or scenarios where this tool is preferred, leaving the agent to infer usage from the name alone.

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