Skip to main content
Glama

search_sketchfab_models

Search and filter 3D models from Sketchfab to import into Blender for 3D modeling projects.

Instructions

Search for models on Sketchfab with optional filtering.

Parameters:

  • query: Text to search for

  • categories: Optional comma-separated list of categories

  • count: Maximum number of results to return (default 20)

  • downloadable: Whether to include only downloadable models (default True)

Returns a formatted list of matching models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
categoriesNo
countNo
downloadableNo

Implementation Reference

  • The search_sketchfab_models function serves as the MCP tool handler. It registers as a tool with @mcp.tool(), parses parameters, and executes the search command via a Blender connection.
    @mcp.tool()
    def search_sketchfab_models(
        ctx: Context,
        query: str,
        categories: str = None,
        count: int = 20,
        downloadable: bool = True
    ) -> str:
        """
        Search for models on Sketchfab with optional filtering.
        
        Parameters:
        - query: Text to search for
        - categories: Optional comma-separated list of categories
        - count: Maximum number of results to return (default 20)
        - downloadable: Whether to include only downloadable models (default True)
        
        Returns a formatted list of matching models.
        """
        try:
            
            blender = get_blender_connection()
            logger.info(f"Searching Sketchfab models with query: {query}, categories: {categories}, count: {count}, downloadable: {downloadable}")
            result = blender.send_command("search_sketchfab_models", {
                "query": query,
                "categories": categories,
                "count": count,
                "downloadable": downloadable
            })
            
            if "error" in result:
                logger.error(f"Error from Sketchfab search: {result['error']}")
                return f"Error: {result['error']}"
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions 'Returns a formatted list' but lacks detail on pagination, rate limits, authentication requirements, or what 'formatted' means (JSON vs string). Defaults are mentioned but also present in schema.

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?

Structured clearly with purpose statement, Parameters section, and Returns section. The parameter list is necessary given schema lacks descriptions. No redundant or wasted sentences, though formal structure slightly reduces information density.

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?

Adequate for a search tool with 4 parameters and no output schema. Describes inputs well and mentions return type vaguely, but missing behavioral context (pagination, result structure) that would help an agent handle the response correctly.

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?

With 0% schema description coverage, the description effectively compensates by explaining all 4 parameters. Adds crucial semantic details not in schema: 'comma-separated list' for categories, 'Maximum number' for count, and 'only downloadable' for downloadable boolean.

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?

States specific verb (Search) and resource (models on Sketchfab) clearly. Distinguishes from siblings by platform name (Sketchfab vs Polyhaven) and action (search vs download), though could explicitly mention the discovery-to-download workflow with download_sketchfab_model.

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

Usage Guidelines2/5

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

No explicit guidance on when to use versus alternatives like search_polyhaven_assets, or prerequisite steps needed before calling this tool. The filtering capabilities are listed but not contextualized within a workflow.

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