Skip to main content
Glama
mikeysrecipes

BlenderMCP

download_sketchfab_model

Download and import 3D models from Sketchfab into Blender using the model's unique identifier (UID).

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 main handler function for the 'download_sketchfab_model' MCP tool. It connects to Blender, sends the download command with the model UID, and processes the result, returning success or error messages.
    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']}")
                return f"Error: {result['error']}"
            
            if result.get("success"):
                imported_objects = result.get("imported_objects", [])
                object_names = ", ".join(imported_objects) if imported_objects else "none"
                return f"Successfully imported model. Created objects: {object_names}"
            else:
                return f"Failed to download model: {result.get('message', 'Unknown error')}"
        except Exception as e:
            logger.error(f"Error downloading Sketchfab model: {str(e)}")
            import traceback
            logger.error(traceback.format_exc())
            return f"Error downloading Sketchfab model: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions that the tool 'downloads and imports' and returns a success/failure message, which implies mutation and output behavior. However, it lacks details on side effects (e.g., where the model is stored, if it overwrites existing files), error handling, or performance aspects like rate limits. For a mutation tool with zero annotation coverage, this is insufficient.

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 description is well-structured and front-loaded with the core purpose, followed by parameter details and prerequisites. It uses three sentences efficiently, with no wasted words. A minor deduction because the prerequisites could be integrated more seamlessly, but overall it's concise and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation operation with one parameter), no annotations, and no output schema, the description is adequate but has gaps. It covers the purpose, parameter meaning, and basic prerequisites, but lacks details on behavioral traits, output format beyond success/failure, and integration with siblings. It meets minimum viability but isn't fully comprehensive.

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 description adds meaningful context for the single parameter: 'uid: The unique identifier of the Sketchfab model.' Since schema description coverage is 0% (the schema only provides title and type), this compensates well by explaining what the UID represents. However, it doesn't specify format or examples (e.g., if it's a numeric ID or alphanumeric string), keeping it from a perfect score.

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 states the tool's purpose: 'Download and import a Sketchfab model by its UID.' It specifies the verb ('download and import'), resource ('Sketchfab model'), and key identifier ('by its UID'). However, it doesn't explicitly differentiate from siblings like 'search_sketchfab_models' or 'import_generated_asset', which prevents a perfect score.

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 implies usage by mentioning prerequisites: 'The model must be downloadable and you must have proper access rights.' This provides some context about when the tool will work, but it doesn't explicitly state when to use this tool versus alternatives like 'search_sketchfab_models' or 'import_generated_asset', nor does it outline exclusions or specific scenarios.

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/mikeysrecipes/blender-mcp'

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