list_videosRetrieve your Recordful videos newest first with IDs, titles, dates, lengths, visibility, and links. Filter by title or set a limit to find specific recordings.
List the user's videos on recordful.app, newest first: videoId, title, date, length, who may watch, and links. Optionally filter by title.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many, newest first (default 10). | |
| query | No | Only videos whose title contains this. |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Although annotations already mark the tool as read-only, the description is valuable because it explicitly lists the fields (e.g., videoId, date, length) that will be returned in the response. This is a key behavioral detail missing from the structured schema.
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?
The definition is highly concise, presenting all necessary information in a single, well-structured sentence without any superfluous words.
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?
It specifies the sorting logic (newest first) and the fields contained in each result, which is crucial given that a full output schema is not provided. It is a strong definition despite the lack of a return schema.
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 description coverage is 100%, so the description doesn't need to compensate for gaps. It is concise but does not add significant semantic meaning beyond what the parameters already state.
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 defines the resource (user's videos), the action (list), and the domain (recordful.app). It clearly distinguishes itself from single-item retrieval functions like get_video.
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?
It identifies filtering by title as an optional feature, which helps clarify usage. However, it does not advise when to use this tool versus other list-related siblings, nor does it define complex use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.