Skip to main content
Glama

List the Blender models on this R3 account

r3_blender_list
Read-onlyIdempotent

List the Blender models this R3 account has uploaded — one per .blend file name, the current version of each — with what it will produce: how many Blender objects land in the scene, how many meshes and materials, its screenshot, and any PENDING update (a re-upload that changes meshes the user's projects use, waiting for r3_blender_update). An upload with unapplied modifiers is applied in Blender by R3 itself; a model says what was applied, per object. community: true lists everyone's public models instead. Add one (or some of its meshes) to a project with r3_blender_import. A .blend gets here two ways: a person uploads it in the R3 app (Models -> Upload .blend), or you save one you built in Blender with r3_blender_upload (a one-time ticket and an upload endpoint: never a tool argument).

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": "r3_blender_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many models to return (default 25, max 100).
cursorNoContinue a list: the nextCursor of the previous page.
searchNoOnly models whose name matches, searched across every model (not the page in hand).
communityNotrue lists the PUBLIC models of every user (the Community tab) instead of this account's own.

Output Schema

NameRequiredDescriptionDefault
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
filterYes
modelsYes
hasMoreYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Only models whose name matches. Prefer this to paging."New value: +"Only models whose name matches, searched across every model (not the page in hand)."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / models / items / properties / yours
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / models / items / required
      Previous value: -[
      -  "blenderModelId",
      -  "name",
      -  "filename",
      -  "owner",
      -  "status",
      -  "currentFileId",
      -  "updatedAt",
      -  "meshCount",
      -  "objectCount",
      -  "isPublic",
      -  "thumbnailUrl",
      -  "previewPending",
      -  "pendingUpdate",
      -  "errorMessage",
      -  "importState",
      -  "legacyReason",
      -  "appliedFromUpload",
      -  "latestUpload"
      -]New value: +[
      +  "blenderModelId",
      +  "name",
      +  "filename",
      +  "owner",
      +  "yours",
      +  "status",
      +  "currentFileId",
      +  "updatedAt",
      +  "meshCount",
      +  "objectCount",
      +  "isPublic",
      +  "thumbnailUrl",
      +  "previewPending",
      +  "pendingUpdate",
      +  "errorMessage",
      +  "importState",
      +  "legacyReason",
      +  "appliedFromUpload",
      +  "latestUpload"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / models / items / properties / importState / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "ok",
      -      "needs_reparse",
      -      "legacy"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ok",
      +      "needs_reparse",
      +      "needs_owner_reparse",
      +      "legacy"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
      +  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "models",
      -  "filter",
      -  "hasMore",
      -  "nextCursor"
      -]New value: +[
      +  "models",
      +  "filter",
      +  "hasMore",
      +  "nextCursor",
      +  "answer"
      +]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive plus openWorldHint, so safety is covered. The description adds real behavioral context beyond them: results include object/mesh/material counts, a screenshot, and any PENDING update that changes meshes projects depend on, and it notes that unapplied modifiers are applied by R3 itself and reported per object. It stops short of describing ordering or behavior on an empty account, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the community override are front-loaded after a slightly long hyphenated opening clause, and every sentence does work. It is on the verbose side for a 4-parameter list tool, with the upload-ticket tangent ('never a tool argument') being useful disambiguation but not essential to invoking this call.

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?

An output schema exists, so return payloads needn't be described, and annotations carry the safety profile; the description still covers alternates, the pending-update state, and where .blend files come from. For a listing tool with four optional parameters this is close to complete, with only ordering and empty-result behavior unaddressed.

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 the schema already documents limit, cursor, search and community. The description restates the community flag's meaning ('public models of every user') but adds no syntax, default, or interaction details beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource ('List the Blender models this R3 account has uploaded') and immediately scopes the granularity: one row per .blend file name, current version only. It also distinguishes itself from the community listing and from r3_blender_import, so an agent can pick it over siblings without opening a schema.

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?

Explicit routing is present: 'community: true lists everyone's public models instead', 'Add one (or some of its meshes) to a project with r3_blender_import', and the two ingestion paths are spelled out including 'r3_blender_upload (a one-time ticket and an upload endpoint: never a tool argument)'. A pending re-upload is tied to r3_blender_update, which is exactly the kind of when-to-use detail agents need.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources