Browse recent Clipy screen recordings, newest first. Filter by processing status and limit results to find specific recordings.
List the user's most recent Clipy screen recordings (newest first). Use this to browse when you don't have a search term.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20). | |
| status | No | Optional filter by processing status. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. It discloses ordering and recency but omits other behaviors like whether only user's recordings are returned, pagination details, or rate limits. Adequate but not comprehensive.
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?
Two short, front-loaded sentences with no wasted words. Efficiently conveys core purpose and usage guidance.
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?
No output schema exists, so description should hint at return structure (e.g., what fields recordings contain). It does not. Also lacks mention of sibling tools beyond implication. Incomplete for a list operation.
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?
Schema coverage is 100%, so parameters are already documented. Description adds context about default ordering and browsing use case but does not enhance parameter meaning further.
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?
The description explicitly states the action (list) and resource (most recent Clipy screen recordings) with a clear ordering (newest first), distinguishing it from sibling tools like search_recordings.
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?
Directly tells when to use this tool ('when you don't have a search term'), implying the alternative (search_recordings) and providing clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.