Blender Bridge

List project results

list_project_files

Read-onlyIdempotent

Discover existing output files in the receiving Desktop application's configured project workspace. Optionally filter kind to scene, render, video or model and cap the number of results with limit. Returns file metadata and workspace-relative paths; remote responses omit absolute disk paths. Requires the receiving Desktop to be running and accessible. Does not create, render or upload a result and does not auto-start Desktop. Use get_project_file with a returned relative path to retrieve a file; view_files is the app-panel adapter.

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_project_files"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Optional output category; omit to list supported result categories together.
`limit`	No	Maximum number of file records to return, from 1 to 200.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / kind / description

Added value: +"Optional output category; omit to list supported result categories together."

addedInput schema / properties / limit / description

Added value: +"Maximum number of file records to return, from 1 to 200."

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive safety, and the description adds genuinely new context: the Desktop must be running and accessible, and remote responses omit absolute disk paths. It stops short of describing error behavior or result counts, so it is strong rather than exhaustive.

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?

Purpose and scope are front-loaded, followed by parameters, return shape, prerequisites, exclusions and alternatives, each in a single dense sentence. No sentence is filler and nothing important is buried.

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?

With no output schema, the description supplies the missing return detail (file metadata plus workspace-relative paths, absolute paths omitted remotely) and the precondition that Desktop must be running. For a 2-optional-parameter read tool this is fully sufficient to call correctly.

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?

Schema description coverage is 100%, so both 'kind' (with its enum) and 'limit' are already documented, including the 1-200 range. The description's mention of kind values and limit merely restates the schema, which is the correct baseline-3 case.

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?

States a specific verb and resource ('Discover existing output files') plus the exact scope ('configured project workspace' of the receiving Desktop). This clearly separates it from get_project_file and view_files, which are named in the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the follow-up tool ('Use get_project_file with a returned relative path to retrieve a file') and the sibling adapter ('view_files is the app-panel adapter'), and rules out misuse with 'Does not create, render or upload a result and does not auto-start Desktop.' Alternatives and exclusions are both present.

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

All Blender Bridge 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?