Skip to main content
Glama
Sign In
BrowserMCP Extended

BrowserMCP Extended

by NEO10111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_clipboard_write

Writes supplied text to the browser clipboard, enabling AI clients to place content on Chrome’s clipboard for pasting into web forms or other apps.

Instructions

Write text to the browser 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": {
      "text": "<text>"
    },
    "name": "browser_clipboard_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to write to the clipboard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/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 but discloses almost nothing: it doesn't say whether writes overwrite existing clipboard content, whether permission grants are needed, whether it works in headless mode, or what happens if no page is open. Only the implicit 'browser clipboard' scope adds information.

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?

A single short sentence with no waste and the action front-loaded. It is appropriately sized, though its brevity reflects under-specification rather than tight editing.

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 a one-parameter tool with full schema coverage and no output schema, the description is minimally sufficient to invoke it correctly. However, with zero annotations it leaves behavioral questions (permissions, overwrite semantics, failure modes) unanswered.

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 the single parameter 'text' is documented in the schema itself. The description adds no format, size, or encoding details beyond what the schema already states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb plus resource ("Write text to the browser clipboard") but essentially restates the tool name browser_clipboard_write with no additional specificity. No sibling tool covers clipboard operations, so differentiation isn't needed, but nothing distinguishes scope, e.g., system clipboard vs page clipboard, beyond the word 'browser'.

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, no preconditions such as requiring a focused page or active tab, and no mention of alternatives like browser_press_key or execute_script for clipboard-adjacent flows.

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