Skip to main content
Glama
opslon

BlenderMCP

by opslon

search_sketchfab_models

Find downloadable 3D models on Sketchfab for Blender projects using search queries and category filters.

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 tool handler, which uses the blender connection to perform the search.
    @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']}"
            
            # Safely get results with fallbacks for None
            if result is None:
                logger.error("Received None result from Sketchfab search")
                return "Error: Received no response from Sketchfab search"
                
            # Format the results
            models = result.get("results", []) or []
            if not models:
                return f"No models found matching '{query}'"
                
            formatted_output = f"Found {len(models)} models matching '{query}':\n\n"
            
            for model in models:
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 tool 'Returns a formatted list of matching models,' which gives some output context, but lacks critical details like rate limits, authentication requirements, pagination behavior, error handling, or whether it's a read-only operation. For a search tool with 4 parameters and no 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 appropriately sized. It starts with a clear purpose statement, then lists parameters with explanations, and ends with return information. Every sentence adds value, with no redundant or wasted text. The bullet-point format enhances readability without being verbose.

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 moderate complexity (4 parameters, no annotations, no output schema), the description is partially complete. It adequately covers parameter semantics and the basic return format, but lacks behavioral context like error cases, rate limits, or authentication needs. Without an output schema, more detail on the 'formatted list' structure would be helpful, making this minimally viable but with clear gaps.

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 significant value beyond the input schema, which has 0% schema description coverage. It explains all 4 parameters with clear semantics: 'query' as text to search for, 'categories' as optional comma-separated list, 'count' as maximum results with default 20, and 'downloadable' as a boolean filter with default True. This fully compensates for the schema's lack of descriptions.

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 as 'Search for models on Sketchfab with optional filtering,' which is a specific verb+resource combination. It distinguishes itself from siblings like 'download_sketchfab_model' by focusing on search rather than download operations. However, it doesn't explicitly differentiate from 'search_polyhaven_assets' beyond the platform name.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search_polyhaven_assets' for cross-platform comparisons, nor does it specify prerequisites or contextual constraints. The only implied usage is for Sketchfab model searches, but no explicit when/when-not instructions are given.

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

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