Skip to main content
Glama

download_sketchfab_model

Import Sketchfab 3D models into Blender with automatic scaling to specified dimensions for consistent scene integration.

Instructions

Download and import a Sketchfab model by its UID. The model will be scaled so its largest dimension equals target_size.

Parameters:

  • uid: The unique identifier of the Sketchfab model

  • target_size: REQUIRED. The target size in Blender units/meters for the largest dimension. You must specify the desired size for the model. Examples: - Chair: target_size=1.0 (1 meter tall) - Table: target_size=0.75 (75cm tall) - Car: target_size=4.5 (4.5 meters long) - Person: target_size=1.7 (1.7 meters tall) - Small object (cup, phone): target_size=0.1 to 0.3

Returns a message with import details including object names, dimensions, and bounding box. The model must be downloadable and you must have proper access rights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes
target_sizeYes

Implementation Reference

  • The function `download_sketchfab_model` acts as the MCP tool handler for downloading and importing Sketchfab models into Blender. It communicates with a Blender connection to perform the actual download and processing.
    def download_sketchfab_model(
        ctx: Context,
        uid: str,
        target_size: float
    ) -> str:
        """
        Download and import a Sketchfab model by its UID.
        The model will be scaled so its largest dimension equals target_size.
        
        Parameters:
        - uid: The unique identifier of the Sketchfab model
        - target_size: REQUIRED. The target size in Blender units/meters for the largest dimension.
                      You must specify the desired size for the model.
                      Examples:
                      - Chair: target_size=1.0 (1 meter tall)
                      - Table: target_size=0.75 (75cm tall)
                      - Car: target_size=4.5 (4.5 meters long)
                      - Person: target_size=1.7 (1.7 meters tall)
                      - Small object (cup, phone): target_size=0.1 to 0.3
        
        Returns a message with import details including object names, dimensions, and bounding box.
        The model must be downloadable and you must have proper access rights.
        """
        try:
            blender = get_blender_connection()
            logger.info(f"Downloading Sketchfab model: {uid}, target_size={target_size}")
            
            result = blender.send_command("download_sketchfab_model", {
                "uid": uid,
                "normalize_size": True,  # Always normalize
                "target_size": target_size
            })
            
            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"
                
                output = f"Successfully imported model.\n"
                output += f"Created objects: {object_names}\n"
                
                # Add dimension info if available
Behavior4/5

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

With no annotations provided, description carries full burden. It discloses critical behavioral trait: automatic scaling so largest dimension equals target_size. It also describes return format ('message with import details') and access constraints, though it omits error handling or side effects like scene overwrite behavior.

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?

Well-structured with front-loaded purpose statement, followed by dedicated Parameters section with formatted examples, and Returns section. Every sentence adds value; no repetition of schema structure or tautology.

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

Completeness5/5

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

Given zero schema descriptions, no annotations, and no output schema, description achieves completeness: fully documents both parameters, explains return value format, describes scaling behavior, and notes access prerequisites. No gaps remain unaddressed.

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

Parameters5/5

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

Schema has 0% description coverage (titles only). Description fully compensates with extensive semantic details: uid defined as unique identifier, target_size explained with units (Blender units/meters) and five concrete domain examples (Chair: 1.0, Car: 4.5, etc.) that clarify expected value ranges.

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?

Description states specific actions (download and import) with specific resource (Sketchfab model by UID), and distinguishes from siblings like search_sketchfab_models and get_sketchfab_model_preview by focusing on the actual import workflow.

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?

Provides prerequisite constraints ('model must be downloadable', 'proper access rights'), but lacks explicit guidance on when to use this tool versus search_sketchfab_models or get_sketchfab_model_preview, or workflow sequencing.

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

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