Skip to main content
Glama
Sign In
pony-browser-mcp

pony-browser-mcp

by pssrh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_paste_from_clipboard

Paste clipboard content into a form field without exposing the content; only the character count is returned. Securely transfer credentials between pages and apps.

Instructions

SECRET-SAFE: Paste the system clipboard into a form field WITHOUT the content ever being returned — only the character count comes back. Pairs with browser_copy_to_clipboard for credential moves between pages/apps. Trims whitespace by default (trim:false to keep).

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": {
      "selector": "<selector>"
    },
    "name": "browser_paste_from_clipboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoTrim surrounding whitespace before pasting (default: true)
selectorYesCSS or text selector for the target input field

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical behavior: content never returns, only character count, and whitespace trimming default. It could add failure behavior but covers the privacy-relevant trait well.

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?

Three short sentences, front-loaded with the most important safety trait and purpose, no filler.

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

Completeness4/5

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

Low-complexity 2-param tool with no output schema; description explains what comes back (only character count) and the default trim behavior, which is sufficient for correct invocation. Minor gap: no mention of failure cases, but not essential.

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 already documents selector and trim with 100% coverage; description reinforces the trim default and how to disable it but adds no meaning beyond schema. Selector semantics are self-explanatory in schema.

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?

States a specific action ('paste system clipboard into a form field') plus its key privacy property and pairing with browser_copy_to_clipboard, so it is clearly distinguishable from fill/click siblings.

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?

Explicitly frames the use case: moving credentials between pages/apps alongside browser_copy_to_clipboard. It does not spell out when to prefer fill or other input methods, but the context is clear enough for tool selection.

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