Skip to main content
Glama

download_sketchfab_model

Download and import 3D models from Sketchfab into Blender using the model's unique identifier, enabling direct access to assets for 3D projects.

Instructions

Download and import a Sketchfab model by its UID.

Parameters:

  • uid: The unique identifier of the Sketchfab model

Returns a message indicating success or failure. The model must be downloadable and you must have proper access rights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes

Implementation Reference

  • The handler function 'download_sketchfab_model' which is registered as an MCP tool and delegates the actual download to a Blender connection via 'blender.send_command'.
    @mcp.tool()
    def download_sketchfab_model(
        ctx: Context,
        uid: str
    ) -> str:
        """
        Download and import a Sketchfab model by its UID.
        
        Parameters:
        - uid: The unique identifier of the Sketchfab model
        
        Returns a message indicating success or failure.
        The model must be downloadable and you must have proper access rights.
        """
        try:
            
            blender = get_blender_connection()
            logger.info(f"Attempting to download Sketchfab model with UID: {uid}")
            
            result = blender.send_command("download_sketchfab_model", {
                "uid": uid
            })
            
            if result is None:
                logger.error("Received None result from Sketchfab download")
                return "Error: Received no response from Sketchfab download request"
                
            if "error" in result:
                logger.error(f"Error from Sketchfab download: {result['error']}")
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return format ('message indicating success or failure') and access requirements. However, it omits other behavioral traits like whether the operation blocks, overwrites existing scene objects, or handles specific error states beyond generic failure.

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 efficiently structured with clear sections: purpose declaration, parameter definition, return value description, and constraints. Every sentence adds value without repetition. The key action is front-loaded in the first sentence.

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?

Given the single parameter and lack of output schema, the description adequately covers the parameter meaning and return type. It could be improved by specifying that 'import' means importing into the current Blender scene (evident from sibling tools like 'get_scene_info'), but the access rights constraint adds necessary completeness for a download operation.

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

Parameters4/5

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

The schema has 0% description coverage (only 'title: Uid'). The description compensates effectively by defining 'uid' as 'The unique identifier of the Sketchfab model', providing necessary semantic meaning. A score of 5 would require additional context like format examples or where to obtain the UID.

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 clearly states the specific action ('Download and import'), resource ('Sketchfab model'), and key parameter ('by its UID'). It effectively distinguishes from siblings like 'search_sketchfab_models' (search vs download) and 'download_polyhaven_asset' (different asset source).

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

Usage Guidelines3/5

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

The description provides prerequisites ('The model must be downloadable and you must have proper access rights'), which helps the agent understand constraints. However, it lacks explicit guidance on when to use this versus 'search_sketchfab_models' (e.g., 'use this after obtaining a UID via search') or versus importing generated assets.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iflow-mcp/Eminemminem-blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server