Skip to main content
Glama

search_polyhaven_assets

Search and filter 3D assets from Polyhaven for use in Blender projects, enabling quick integration of HDRI, textures, and models into 3D scenes.

Instructions

Search for assets on Polyhaven with optional filtering.

Parameters:

  • asset_type: Type of assets to search for (hdris, textures, models, all)

  • categories: Optional comma-separated list of categories to filter by

Returns a list of matching assets with basic information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_typeNoall
categoriesNo

Implementation Reference

  • This is the handler function for the MCP tool 'search_polyhaven_assets'. It is registered via the @mcp.tool() decorator. The function connects to a Blender addon via socket, sends the search parameters, receives the raw asset data from PolyHaven, formats it into a user-friendly string (sorted by download count), and returns it. Type hints provide the input schema.
    @mcp.tool()
    def search_polyhaven_assets(
        ctx: Context,
        asset_type: str = "all",
        categories: str = None
    ) -> str:
        """
        Search for assets on Polyhaven with optional filtering.
        
        Parameters:
        - asset_type: Type of assets to search for (hdris, textures, models, all)
        - categories: Optional comma-separated list of categories to filter by
        
        Returns a list of matching assets with basic information.
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("search_polyhaven_assets", {
                "asset_type": asset_type,
                "categories": categories
            })
            
            if "error" in result:
                return f"Error: {result['error']}"
            
            # Format the assets in a more readable way
            assets = result["assets"]
            total_count = result["total_count"]
            returned_count = result["returned_count"]
            
            formatted_output = f"Found {total_count} assets"
            if categories:
                formatted_output += f" in categories: {categories}"
            formatted_output += f"\nShowing {returned_count} assets:\n\n"
            
            # Sort assets by download count (popularity)
            sorted_assets = sorted(assets.items(), key=lambda x: x[1].get("download_count", 0), reverse=True)
            
            for asset_id, asset_data in sorted_assets:
                formatted_output += f"- {asset_data.get('name', asset_id)} (ID: {asset_id})\n"
                formatted_output += f"  Type: {['HDRI', 'Texture', 'Model'][asset_data.get('type', 0)]}\n"
                formatted_output += f"  Categories: {', '.join(asset_data.get('categories', []))}\n"
                formatted_output += f"  Downloads: {asset_data.get('download_count', 'Unknown')}\n\n"
            
            return formatted_output
        except Exception as e:
            logger.error(f"Error searching Polyhaven assets: {str(e)}")
            return f"Error searching Polyhaven assets: {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 full burden. It mentions that the tool 'returns a list of matching assets with basic information', which gives some behavioral context about the output. However, it doesn't disclose important traits like whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior, or what 'basic information' entails. For a search tool with zero annotation coverage, this leaves significant gaps.

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 with three sentences: a purpose statement, parameter explanations, and return information. It's front-loaded with the core functionality. While efficient, the parameter section could be slightly more structured, but overall there's minimal waste.

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 2 parameters with 0% schema coverage and no output schema, the description provides adequate but incomplete coverage. It explains parameter purposes and mentions the return type, but doesn't detail the structure of returned assets, error conditions, or search behavior limitations. For a search tool with no annotations, it meets minimum viable standards but has clear gaps in behavioral context.

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%, so the description must compensate. It provides meaningful semantics for both parameters: 'asset_type' is explained as 'Type of assets to search for (hdris, textures, models, all)' and 'categories' as 'Optional comma-separated list of categories to filter by'. This adds crucial context beyond the bare schema, though it doesn't specify format details or provide examples for the categories parameter.

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 searches for assets on Polyhaven with filtering, which is a specific verb (search) and resource (assets on Polyhaven). It distinguishes from siblings like 'download_polyhaven_asset' (which retrieves specific assets) and 'search_sketchfab_models' (which searches a different platform), though it doesn't explicitly mention these distinctions.

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 for searching assets with optional filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'search_sketchfab_models' or 'get_polyhaven_categories'. It mentions filtering capabilities, which gives some context, but lacks clear when/when-not instructions or prerequisite information.

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

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