chatgpt-remote-browser-mcp

Type in shared browser tab

type

Type text into a specified element on the active browser tab, updating the page or external site state directly.

Instructions

Type text into an element in a currently shared tab. This changes browser or external-site state.

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>",
      "ref": "<ref>",
      "text": "<text>"
    },
    "name": "type"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes
`text`	Yes
`handle`	Yes
`slowly`	No
`submit`	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?

The description notes that typing 'changes browser or external-site state,' which adds some context, but the annotations already indicate readOnlyHint=false and destructiveHint=false. No additional behavioral details are provided about optional parameters like slowly or submit.

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 very concise and well-structured, with no redundant information or excessive detail. It efficiently conveys the core functionality.

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

Completeness1/5

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

The description lacks essential context for correct usage, including parameter explanations, when to use it instead of alternatives, and potential side effects beyond a generic state-change warning. An agent would need to infer much of the behavior.

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 does not explain any of the five parameters. While handle, ref, and text are somewhat self-explanatory, slowly and submit are ambiguous without further detail.

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 ('Type text into an element') and the context ('in a currently shared tab'), providing a specific verb and resource. It is distinct from sibling tools like click and press, though it does not explicitly name them.

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

Usage Guidelines1/5

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 such as click or press. It only mentions a side-effect, not usage context.

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

Deploy Server