clippy

List Clippy Room Items

list-items-tool

Read-onlyIdempotent

Read the items in a Clippy room (newest first). Use this to pick up text a user or another agent left for you, or to see what is currently in a shared room. Pass since (a millisecond timestamp from a previous call) to fetch only items added after that point. Image items include direct image URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link).
`limit`	No	Optional. Maximum number of items to return (1–100). Defaults to 100.
`since`	No	Optional. Return only items created strictly after this Unix timestamp in milliseconds. Use the `now` value from a previous call to poll incrementally.
`password`	No	Required only if the room is password-protected and you are not using owner_token.
`owner_token`	No	Optional. The room owner_token; bypasses the password on a locked room.

Output Schema

TableJSON Schema

Name	Required	Description
`now`	Yes	Server time in Unix milliseconds; pass as `since` next call to poll incrementally.
`code`	Yes	The room code that was read.
`count`	Yes	Number of items returned.
`items`	Yes	The matching items, newest first.
`locked`	Yes	Whether the room is password-protected.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds ordering, that image items contain direct URLs, and incremental polling use of `since`. No contradiction.

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 concise sentences, no fluff. Front-loaded with purpose and key usage context.

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?

With annotations and output schema, description covers main use cases, filtering, and image note. Could mention password/owner_token in usage but schema handles it.

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 baseline is 3. Description adds value by explaining `since` usage and noting image URLs, aiding correct invocation.

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?

Description uses specific verb 'Read' and resource 'items in a Clippy room' with ordering 'newest first'. Clearly distinguishes from sibling tools like store-item-tool and delete-item-tool.

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 states when to use: to pick up text or see room contents. Provides guidance on `since` for incremental polling. Does not explicitly exclude alternatives.

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

All clippy tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: room creation, text/image storage, item listing, deletion, password management, and room status checking. No two tools overlap in functionality; descriptions make the differences obvious.

Naming Consistency5/5

All tool names follow a consistent kebab-case verb-noun-tool pattern (e.g., clear-room-tool, store-item-tool), making the naming predictable and easy to understand.

Tool Count5/5

With 9 tools, the server covers the core operations needed for a shared clipboard room without being excessive or too sparse. Each tool serves a necessary function in the workflow.

Completeness5/5

The tool set provides full lifecycle coverage: create room, store text/images, list items, update text, delete individual/clear all items, set password, and check room status. No obvious gaps for the intended domain.

Resources

Need Help?