Skip to main content
Glama

list_liquid_objects

Retrieve all available Shopify Liquid objects organized by category to identify variables and data accessible in Liquid templates.

Instructions

List all available Shopify Liquid objects.

Returns: List of all object names with titles organized by category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_liquid_objects' tool, decorated with @mcp.tool() for registration. Retrieves Liquid objects from the documentation database and formats them into categorized lists (Core, Product Related, Cart & Checkout, etc.).
    @mcp.tool()
    def list_liquid_objects() -> str:
        """List all available Shopify Liquid objects.
    
        Returns:
            List of all object names with titles organized by category
        """
        docs = get_by_category("objects")
    
        if not docs:
            return "No objects found in database"
    
        output = [f"Available Liquid Objects ({len(docs)} total):\n"]
    
        # Group by category
        core = []
        product_related = []
        cart_related = []
        customer_related = []
        content = []
        other_objects = []
    
        for doc in docs:
            name = doc["name"]
            title = doc["title"]
            item = f"- **{name}**: {title}"
    
            if name in ["shop", "settings", "theme", "request", "routes"]:
                core.append(item)
            elif "product" in name or "variant" in name or "collection" in name:
                product_related.append(item)
            elif "cart" in name or "checkout" in name or "line_item" in name:
                cart_related.append(item)
            elif "customer" in name or "company" in name:
                customer_related.append(item)
            elif name in ["page", "blog", "article", "articles", "comment"]:
                content.append(item)
            else:
                other_objects.append(item)
    
        if core:
            output.append("**Core Objects:**")
            output.extend(core)
            output.append("")
    
        if product_related:
            output.append("**Product Related:**")
            output.extend(product_related)
            output.append("")
    
        if cart_related:
            output.append("**Cart & Checkout:**")
            output.extend(cart_related)
            output.append("")
    
        if customer_related:
            output.append("**Customer Related:**")
            output.extend(customer_related)
            output.append("")
    
        if content:
            output.append("**Content:**")
            output.extend(content)
            output.append("")
    
        if other_objects:
            output.append("**Other Objects:**")
            output.extend(other_objects[:15])
            if len(other_objects) > 15:
                output.append(f"  ... and {len(other_objects) - 15} more")
    
        return "\n".join(output)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists objects and returns them organized by category, but lacks details on permissions, rate limits, pagination, or error handling. For a read-only tool with no annotations, this is a significant gap in transparency about operational 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?

The description is extremely concise and front-loaded: the first sentence states the core purpose, and the second clarifies the return format. Every sentence earns its place with no wasted words, making it easy for an agent to parse quickly.

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 low complexity (0 parameters, read-only operation) and the presence of an output schema, the description is minimally adequate. It covers the purpose and return format but lacks behavioral context (e.g., permissions, limitations) and usage guidelines relative to siblings. It meets basic needs but leaves gaps that could hinder optimal tool selection.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by explaining the return format ('List of all object names with titles organized by category'), which compensates for the absence of an output schema in the context signals (though 'Has output schema: true' is noted, the description still provides useful semantics). Baseline is high due to no parameters.

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: 'List all available Shopify Liquid objects' with a specific verb ('List') and resource ('Shopify Liquid objects'). It distinguishes from siblings like 'get_liquid_object' (singular) and 'list_liquid_filters/tags' (different resource types), though it doesn't explicitly contrast them. The purpose is unambiguous but could be more precise about sibling differentiation.

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 guidance is provided on when to use this tool versus alternatives. The description mentions the return format but doesn't specify contexts (e.g., for reference vs. search), prerequisites, or exclusions. With siblings like 'search_liquid_docs' and 'get_liquid_object', the lack of usage guidelines leaves the agent to infer appropriate scenarios.

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/florinel-chis/shopify-liquid-mcp'

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