Skip to main content
Glama
Sign In
chatgpt-remote-browser-mcp

chatgpt-remote-browser-mcp

by TommyFive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read shared browser tab

snapshot
Read-only

Retrieve the accessible structure and text of a shared browser tab to enable content analysis and interaction planning.

Instructions

Read the accessible page structure and text from a currently shared tab.

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": {
      "handle": "<handle>"
    },
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
formatNoai
handleYes
interactiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior4/5

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

The description's 'Read' is consistent with the readOnlyHint=true and destructiveHint=false annotations. It adds useful context that the tab must be 'currently shared,' but it does not mention potential return details or any parameter-dependent behavior.

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 a single, focused sentence with no redundant wording. It front-loads the core purpose and is easy to parse.

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?

The description is too sparse to cover the tool's parameter semantics; it does not explain the format enum values, the limit bounds, or the interactive flag, leaving important gaps for correct usage.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no explanation of handle, limit, format, or interactive. None of the parameters' meanings, defaults, or constraints are conveyed.

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 action ('Read'), the target ('accessible page structure and text'), and the specific scope ('currently shared tab'). This distinguishes it from visual tools like screenshot and navigation tools like navigate.

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

Usage Guidelines3/5

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

The description implies usage for extracting text/structure from the shared tab, but it does not explicitly explain when to prefer this tool over siblings such as screenshot or list_shared_tabs. The guidance is left to inference.

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