Skip to main content
Glama

search_sketchfab_models

Find downloadable 3D models on Sketchfab with category filtering for use in Blender 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 implementation of the search_sketchfab_models tool which acts as a wrapper to send the command to the Blender instance.
    @telemetry_tool("search_sketchfab_models")
    @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:
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully documents default values and states it 'Returns a formatted list,' providing some output context. However, it lacks safety information (read-only status), rate limits, or pagination 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 well-structured with a clear purpose statement upfront, followed by parameter documentation and return value information. Every sentence adds value, and the formatting is clean despite being embedded in description text.

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 0% schema coverage and no output schema, the description adequately covers the 4 parameters and mentions the return type. However, it lacks detail on the return value structure (what fields constitute a 'formatted list') and valid category values, leaving gaps for a search tool.

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?

Schema description coverage is 0%, requiring the description to compensate. It excellently documents all 4 parameters, including critical format constraints like 'comma-separated' for categories and semantic context like 'Maximum number of results' for count.

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 states a specific verb ('Search'), resource ('models on Sketchfab'), and scope ('optional filtering'). While clear, it does not explicitly differentiate from sibling tools like download_sketchfab_model or get_sketchfab_model_preview.

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 (e.g., when to search vs. directly downloading) or any prerequisites. The phrase 'optional filtering' implies capability but not usage context.

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