Skip to main content
Glama

browser_clipboard

Read-onlyIdempotent

Read (action='read') or write (action='write', text) the browser's clipboard as text, for pages that copy something to it (a 'Copy link' button) or paste from it. Grants the page's origin clipboard permission first.

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": {
      "page_id": "<page_id>",
      "action": "<action>"
    },
    "name": "browser_clipboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
actionYes
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description explicitly advertises a write mode (`action`='write', `text`) that mutates the clipboard. That is a direct contradiction of the read-only claim. The one genuinely useful behavioral addition, that the tool grants the page's origin clipboard permission first, does not outweigh the conflict.

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 front-loaded sentence that leads with the read/write branching and the parameter values, then the use case, then the permission side effect. The nested parentheticals make it dense on first read, but there is no filler and nothing repeated from the schema.

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?

With no output schema, the description does not say what a read returns when the clipboard is empty, nor what happens if the permission grant is denied. It also leaves the workspace-override parameter unexplained. The core read/write contract and the permission side effect are covered, which is adequate but not complete for a 4-parameter tool.

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 only 25%, so the description must carry weight, and it does explain the two most important parameters: the read/write values of `action` and the role of `text` as the write payload. It says nothing about `page_id` or the `in_workspace` override, and it does not state whether `text` is ignored or required on read, so it only partially compensates for the coverage gap.

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 gives a concrete verb pair (read/write) and a concrete resource (the browser's clipboard as text), and spells out which action value selects each mode. It distinguishes itself from page-content tools by naming the clipboard, though it never contrasts itself with the sibling clipboard_copy, which an agent could easily confuse it with.

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

Usage Guidelines4/5

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

It supplies a real use-case trigger: pages that copy something to the clipboard (a 'Copy link' button) or paste from it, which tells the agent the operation must be driven through the page context rather than as a standalone utility. There are no exclusions or explicit alternatives such as clipboard_copy, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.