Skip to main content
Glama
Eminemminem

BlenderMCP

by Eminemminem

download_sketchfab_model

Download and import 3D models from Sketchfab into Blender using the model's unique identifier for AI-assisted 3D scene creation.

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 MCP tool handler function 'download_sketchfab_model'. It proxies the download request with the given UID to the Blender addon via socket, processes the response, and returns a success message with imported object names or an error.
    @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']}")
                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)}"
  • Docstring defining the tool's input schema (uid: str) and output (str message).
    """
    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.
    """
  • The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
  • Documentation in the asset_creation_strategy prompt referencing the tool usage.
    - Then download specific models using download_sketchfab_model() with the UID
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the model must be downloadable and requires proper access rights, which adds some context about permissions and constraints. However, it lacks details on side effects (e.g., where the model is stored, if it modifies state), rate limits, error handling, or what 'import' entails operationally, leaving significant gaps for a tool that likely involves external API calls and file operations.

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 front-loaded with the core action, followed by parameter and return details in a structured format. It avoids unnecessary fluff, but the second sentence about success/failure could be more integrated, and the access note feels slightly tacked on rather than seamlessly part of the flow.

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 no annotations, no output schema, and low schema coverage, the description is minimally adequate. It covers the basic purpose, parameter meaning, and hints at behavioral constraints (downloadable, access rights), but lacks details on return values beyond success/failure messages, error cases, or integration with sibling tools like 'import_generated_asset', leaving room for improvement in guiding the agent.

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' by specifying it as 'the unique identifier of the Sketchfab model', which clarifies its purpose beyond the schema's basic string type. With 0% schema description coverage and only 1 parameter, this compensates adequately, though it doesn't provide format examples or validation rules.

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 verb 'download and import' and the resource 'Sketchfab model by its UID', making the purpose unambiguous. It distinguishes from siblings like 'search_sketchfab_models' by focusing on retrieval rather than discovery, though it doesn't explicitly mention sibling differentiation.

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 when you have a specific model UID and want to download it, but lacks explicit guidance on when to use this versus alternatives like 'import_generated_asset' or prerequisites beyond access rights. It mentions access rights as a condition, but doesn't detail when-not scenarios or direct comparisons to siblings.

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

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