Retrieve recent clipboard history entries with an optional limit to control how many items are returned. Use it to review or reuse previously copied text and content.
List recent clipboard history entries
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max entries to return (default 20) |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only the word 'recent', with no mention of ordering, truncation behavior, or what an entry contains — minimal added context beyond structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no waste and the scope word front-loaded. It is arguably under-specified rather than bloated, but structurally clean.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a trivial read-only list tool with full schema coverage and annotations, this is adequate but leaves open how results are ordered and what fields an entry has, which matters for an agent deciding between it and paste_from_history.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter and schema coverage is 100%; the schema already documents 'limit' with its default of 20. The description adds nothing about ordering or whether limit caps a broader history, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('clipboard history entries') with a scope qualifier ('recent'). It is distinguishable from siblings like clear_clipboard_history or delete_clipboard_entry, but does not explicitly differentiate from get_clipboard or paste_from_history, which also read clipboard state.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus get_clipboard (current entry) or paste_from_history (restore an entry). The agent must infer the distinction from names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.