Framevine

List library files

list_library_files

Read-onlyIdempotent

List files in the user's library (uploads and generated outputs), paged. Each item has its file id, media kind, MIME type, name, size, purpose, media URL and creation time. Use a file id as an input to generation tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_library_files"
  }
}

Input Schema

Name	Required	Description
`page`	No	Zero-based page number (default 0).
`sort`	No	Sort order (default CREATED_DESC).
`purpose`	No	Only user uploads, or only generated outputs.
`pageSize`	No	Files per page (default 20).
`mediaKind`	No	Only files of this media kind.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint: true, destructiveHint: false), the description provides crucial operational context: the tool is paged, and it lists every field returned (id, MIME type, size, purpose, URL, etc.). This tells the agent exactly what kind of data structure to expect.

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?

The description is concise, front-loaded with the core functionality and scope, and highly efficient. Every phrase contributes to the agent's understanding of the tool's scope and return data.

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?

Since no output schema is provided, the description is highly complete by enumerating all the fields an item contains (ID, media kind, size, purpose, URL, etc.). This leaves no ambiguity regarding the data structure returned.

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

Parameters3/5

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

The schema description coverage is 100%, which sets the baseline score at 3. While the description covers the concepts of 'uploads' vs 'generated outputs,' it does not add specific semantic depth to the parameters themselves beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('List files') and the resource ('user's library'), encompassing both uploads and generated outputs. This scope distinguishes it well from general 'list' tools like list_folders.

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?

It provides a specific functional guideline: the retrieved file id should be used as input to generation tools. This effectively describes the downstream purpose of the tool's output.

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

All Framevine tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?