chatgpt-remote-browser-mcp

Screenshot shared browser tab

screenshot

Read-only

Capture a screenshot of the currently shared browser tab, with options for image format, full-page capture, and UI labels.

Instructions

Capture an image of 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": "screenshot"
  }
}

Input Schema

Name	Required	Default
`type`	No	png
`handle`	Yes
`labels`	No
`fullPage`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Sep 8, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false), and the description is consistent with them—no contradiction. The description adds only the 'currently shared' context but does not disclose output format, what the captured image contains, or edge-case behavior when the tab is unavailable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no waste, which is good, but it borders on under-specification rather than disciplined conciseness. There is room to add value without bloating the text.

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?

For a tool with 4 parameters (1 required), zero parameter descriptions, and no output schema, a one-line description is inadequate. The agent lacks information on the return value (where/how the image is returned), the meaning of labels and fullPage, and the behavior when the handle references an unshared tab.

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?

Schema description coverage is 0%, so the description must compensate, but it mentions none of the four parameters. An agent gets no explanation of what 'labels' does, what 'fullPage' changes, or how 'type' and 'handle' interact, leaving significant ambiguity that the schema alone cannot resolve.

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 verb ('Capture') and resource ('an image of a currently shared tab'), so the core action is clear. However, there is a sibling tool named 'snapshot' whose purpose could overlap, and the description does nothing to differentiate screenshot from it, leaving an agent to guess which to use.

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 alternatives, no prerequisites stated, and no exclusions. The phrase 'currently shared tab' implies a precondition but does not explicitly state it as a requirement or describe what happens if the tab is not shared.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server