Skip to main content
Glama
CrossPaste

CrossPaste

Official
by CrossPaste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search_clipboard

Read-onlyIdempotent

Find clipboard items by keyword, type, or tag, or list recent entries. Read-only results include metadata and summaries; use an ID to get full content.

Instructions

Search or browse the local clipboard history. Read-only. Returns up to 'limit' items (default 20, max 100), newest first, each with its numeric ID, type, source app, favorite flag, size, creation time and a one-line summary; pass an ID to get_paste_item for the full content. Omit 'query' to list the most recent items; otherwise every keyword must match as a prefix of a word in the item's searchable text. 'type' and 'tag' narrow the results and can be combined; tag names come from list_tags. An unknown 'type' or 'tag' returns an error rather than an empty list. Use get_clipboard_stats for counts only and add_to_clipboard to create items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOnly return items carrying this tag, by exact tag name as shown by list_tags (e.g. 'Favorite').
typeNoOnly return items of this type: text, link, image, rtf, html, color, file (case-insensitive; note that URLs are type 'link').
limitNoMaximum number of results, 1-100 (default 20; out-of-range values are clamped)
queryNoSpace-separated keywords, prefix-matched (e.g. 'invoice 2026'). Omit or leave empty to list recent items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default: 20, max: 100)"New value: +"Maximum number of results, 1-100 (default 20; out-of-range values are clamped)"
    • changedInput schema / properties / query / description
      Previous value: -"Search keywords (optional, empty returns recent items)"New value: +"Space-separated keywords, prefix-matched (e.g. 'invoice 2026'). Omit or leave empty to list recent items."
    • changedInput schema / properties / tag / description
      Previous value: -"Filter by tag name (e.g. 'Favorite')"New value: +"Only return items carrying this tag, by exact tag name as shown by list_tags (e.g. 'Favorite')."
    • changedInput schema / properties / type / description
      Previous value: -"Filter by paste type: text, link, image, rtf, html, color, file"New value: +"Only return items of this type: text, link, image, rtf, html, color, file (case-insensitive; note that URLs are type 'link')."
  2. First observedv2.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses return shape and cardinality (up to 'limit' items, default 20, max 100, newest first, field list), matching semantics (every keyword must prefix-match a word in the searchable text), combination rules for 'type' and 'tag', and the notable error behavior for unknown type/tag instead of an empty list.

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-loaded with purpose and read-only status, then return shape, then filtering rules, then sibling routing. Dense and mostly waste-free, though the limit/default/max clause and parts of the return-field list duplicate the schema and could be trimmed.

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?

With no output schema, the description compensates by enumerating returned fields and ordering, plus the error mode for unknown type/tag and the handoff to get_paste_item for full content. An agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: prefix-match semantics across multiple keywords, the coupling of 'query' omission with listing recent items, and the pointer to list_tags as the source of valid tag names. It does not add much on 'limit' beyond repeating the documented default/max.

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 verb and resource ('Search or browse the local clipboard history') and immediately scopes it with 'Read-only.' It is clearly distinguishable from siblings like get_clipboard_stats (counts), add_to_clipboard (writes) and get_paste_item (full content by ID), all of which are named.

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?

Gives explicit routing rules: omit 'query' to browse recent items, pass an ID to get_paste_item for full content, use get_clipboard_stats for counts only, use add_to_clipboard to create items, and get tag names from list_tags. When-to-use and when-to-use-something-else are both covered.

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