Skip to main content
Glama

browser_paste

Inserts text, Markdown source, or HTML directly into a specified or focused browser editor without using the system clipboard, enabling automated form and content entry.

Instructions

Paste text, Markdown source or HTML into the target or focused editor. Does not use the system clipboard.

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": {
      "tabId": "<tabId>",
      "text": "<text>"
    },
    "name": "browser_paste"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
textYes
tabIdYesTab id from browser_tabs.
expectNoPost-action condition. Default timeout is 1.2 seconds in visible pages and 3 seconds in hidden pages. A mismatch does not undo the action; inspect before retrying.
formatNotext
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
revisionNoReject if the DOM revision differs from the snapshot.
selectorNoCSS selector. Must identify exactly one element.
inputModeNoAuto uses trusted Chrome text insertion only in the active foreground tab; DOM otherwise. Pointer actions and keys always use DOM.auto
documentIdNoReject the action if this snapshot document has changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool does not use the system clipboard, but it does not explain mutation effects, event behavior, trusted versus DOM insertion, or permissions.

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 two tightly written sentences with no wasted wording. The primary purpose is front-loaded, followed immediately by the key clipboard caveat.

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

Completeness3/5

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

For an 11-parameter browser action with no annotations and no output schema, the description is thin on behavioral context. The rich input schema compensates substantially for parameter details, but usage guidance and paste behavior remain under-explained.

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 description coverage is high at 82%, so the schema already documents most parameters including ref, selector, inputMode, and expect. The description adds little parameter meaning beyond mentioning text, Markdown, and HTML, which loosely maps to the format enum.

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 and resource: paste text, Markdown source or HTML into a target or focused editor. This is clear, but it does not explicitly differentiate the action from siblings such as browser_fill or browser_click.

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?

Usage is only implicitly indicated by naming the target or focused editor. The description does not state when to prefer this tool over browser_fill or other input tools, nor does it provide exclusions or prerequisites.

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