Skip to main content
Glama

Paste text

paste_text

Insert text into the focused window by copying it to the clipboard and pressing paste as one step — up to 8192 bytes of UTF-8, Linux desktops only.

Instructions

Put text on the desktop clipboard and press the paste shortcut, as one step: the fast way to insert up to 8192 bytes of UTF-8, including accents, CJK and emoji, into whatever has focus. Linux desktops only; Windows and a guest without working clipboard support are refused. The paste REPLACES the clipboard and leaves the text there — after pasting a secret, clear it with write_clipboard and text "". A success means the clipboard write and the shortcut were delivered, not that the application inserted the text (a paste-disabled field ignores it): check with a screenshot. An interrupted call may already have pasted, so look before sending it again, and do not fall back to type_text without looking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to paste: 1 to 8192 bytes of UTF-8, no NUL.
contextNoAnswer the desktop's windows, and which one has focus, as they stand just after the action — what list_windows would say, without a second call — and, when the focused window is Chromium, the page on screen: its URL, title and the interactive elements visible in it, each with the point to click. Read at once, so a window still opening may not be listed yet. If they cannot be read the action still happened, and the answer says why.
shortcutNo"ctrl+v" (the default) or "ctrl+shift+v", which terminals need. Shift+Insert is not offered: it can paste the separate primary selection instead.
computer_idNoWhich computer. Defaults to the one selected with use_computer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.6/5.0
Behavior5/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 so richly: Linux-only with Windows/guests refused, clipboard is REPLACED and left behind, success means 'delivered' not 'inserted' (paste-disabled fields ignore it), and an interrupted call may already have pasted. These are exactly the side-effect and idempotency disclosures an agent needs for a mutation tool.

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?

Front-loads the action and then layers constraints, with every sentence carrying operational weight (platform limits, secret cleanup, success semantics, retry caution). It is dense and long, but no line is filler; slightly tighter grouping would earn a 5.

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

Completeness5/5

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

No output schema and no annotations exist, yet the description fully covers platform eligibility, clipboard side effects, what 'success' actually guarantees, verification method, and interrupted-call recovery. Nothing essential for correct invocation is missing.

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%, so the schema already documents all four parameters including the shortcut enum rationale and the context flag. The description adds only minor emphasis (the 8192-byte limit) that 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.

Purpose5/5

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

States a specific compound action (write clipboard + press paste shortcut) with scope (up to 8192 bytes UTF-8, into whatever has focus) and platform constraints. It is clearly distinguishable from siblings write_clipboard, type_text, and press_key, which the description explicitly references.

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

Usage Guidelines5/5

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

Explicitly names the alternative paths and their conditions: clear a pasted secret with write_clipboard + empty text, verify with a screenshot rather than assuming success, and do not fall back to type_text without looking. This routes the agent correctly across multiple sibling tools.

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