Skip to main content
Glama

download_sketchfab_model

Download and import 3D models from Sketchfab directly 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

  • Handler function for the 'download_sketchfab_model' MCP tool. It connects to Blender, sends the download command with the model UID, and processes the response, returning success or error messages.
    @telemetry_tool("download_sketchfab_model")
    @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)}"
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 access rights and downloadability, which adds some behavioral context, but it doesn't disclose critical traits like whether this is a read-only or destructive operation, potential rate limits, error handling, or what 'import' entails (e.g., file format, storage location). This leaves significant gaps for an agent to understand the tool's behavior.

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 appropriately sized and front-loaded, starting with the core action. The sentences are efficient, but the second sentence about returns could be integrated more smoothly, and the prerequisites are listed without unnecessary elaboration, making it mostly concise with minor room for improvement.

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

Completeness2/5

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

Given the complexity of a download/import operation, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on output format beyond a success/failure message, error conditions, what 'import' means in practice, and how it interacts with sibling tools. This makes it inadequate for full agent understanding.

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 description coverage is 0%, so the description must compensate. It provides the parameter 'uid' with a clear explanation ('The unique identifier of the Sketchfab model'), adding essential meaning beyond the bare schema. However, it doesn't specify the format or constraints of the UID (e.g., length, pattern), which could be helpful, so it's not 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 action ('Download and import') and the resource ('a Sketchfab model by its UID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_sketchfab_models' or 'import_generated_asset', which could handle similar resources or steps, so it falls short of 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'), but it doesn't explicitly state when to use this tool versus alternatives like 'search_sketchfab_models' for finding models or 'import_generated_asset' for importing. This provides some context but lacks clear differentiation.

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

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