Skip to main content
Glama
sellersmith

TailorKit MCP

Official
by sellersmith

get_list_templates

Retrieve customizable product templates for a Shopify store by specifying domain, limit, page, sort, and filter parameters to streamline e-commerce template management.

Instructions

Get list templates with shop domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoThe filter
limitNoThe limit of the templates
pageNoThe page number
shopDomainNoThe shop domain ends with .myshopify.com
sortNoThe sort orderupdatedAt__desc

Implementation Reference

  • Implementation of the get_list_templates tool handler, which validates arguments and delegates to the template service's getListTemplates method.
    /**
     * Validate getListTemplates arguments
     */
    function validateGetListTemplatesArgs(args: GetListTemplatesArgs): void {
      validateCommonToolArgs(args);
    }
    
    /**
     * Service method for getListTemplates
     */
    async function getListTemplatesServiceMethod(
      serviceManager: ServiceManager,
      args: GetListTemplatesArgs
    ) {
      return serviceManager.templateService.getListTemplates(args);
    }
    
    /**
     * Handler for get_list_templates tool
     */
    export const getListTemplatesHandler = createHandler<GetListTemplatesArgs, any>(
      validateGetListTemplatesArgs,
      getListTemplatesServiceMethod
    );
  • Input schema and metadata definition for the get_list_templates tool.
    const getListTemplatesTool: TailorKitTool = {
      name: TAILOR_KIT_TOOL_NAMES.GET_LIST_TEMPLATES,
      description: "Get list templates with shop domain",
      inputSchema: {
        type: "object",
        properties: {
          shopDomain: {
            type: "string",
            description: "The shop domain ends with .myshopify.com",
          },
          limit: {
            type: "number",
            description: "The limit of the templates",
            default: 5,
          },
          page: {
            type: "number",
            description: "The page number",
            default: 1,
          },
          sort: {
            type: "string",
            description: "The sort order",
            default: "updatedAt__desc",
          },
          filter: {
            type: "string",
            description: "The filter",
            format: "string__has__",
          },
          ...COMMON_TOOL_PROPERTIES,
        },
        required: ["shopDomain", "prompt", "conversationId", "conversationTitle"],
      },
    };
  • Registration of the getListTemplatesHandler for the 'get_list_templates' tool name in the handler registry.
    this.registry.register(
      TAILOR_KIT_TOOL_NAMES.GET_LIST_TEMPLATES,
      (args: unknown) => getListTemplatesHandler(this.serviceManager, args)
    );
  • Import and registration of the getListTemplatesTool in the main tools export.
    import getListTemplatesTool from "./template/getListTemplatesTool.js";
    import getDetailProductTool from "./shopify/products/getDetailProductTool.js";
    import { getListProductsTool } from "./shopify/products/index.js";
    import getUserPreferencesTool from "./userPreferences/getUserPreferencesTool.js";
    
    const TOOLS = [
      getListTemplatesTool,
  • TypeScript interface defining the shape of arguments for the get_list_templates tool.
    export interface GetListTemplatesArgs extends CommonToolArgs {
      /**
       * The limit of the templates
       * Default: 5
       */
      limit?: number;
    
      /**
       * The page number
       * Default: 1
       */
      page?: number;
    
      /**
       * The sort order
       * Default: "updatedAt__desc"
       */
      sort?: "updatedAt__asc" | "updatedAt__desc" | "name__asc" | "name__desc";
    
      /**
       * The filter name
       * Format: string__has__{value}
       */
      filter?: string;
    }
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 mentions the required 'shop domain' context but fails to describe critical behaviors: whether this is a read-only operation, if it requires authentication, how pagination works with 'limit' and 'page', or what the return format looks like. For a list retrieval 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and includes essential context ('with shop domain'). Every part earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is incomplete. It lacks information on return values, error handling, authentication needs, and how parameters like 'filter' and 'sort' function. Without annotations or output schema, the agent has insufficient context to use the tool effectively beyond basic parameter passing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds minimal value beyond implying that 'shopDomain' is required (though it's not marked as required in the schema). It doesn't explain parameter interactions or provide additional context beyond what's in the schema, meeting the baseline for high coverage.

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 verb ('Get') and resource ('list templates'), making the purpose understandable. It specifies the required context ('with shop domain'), which helps differentiate it from generic template retrieval tools. However, it doesn't explicitly distinguish from sibling tools like 'get_detail_template' or 'get_list_layers_of_template', preventing a perfect score.

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 'get_detail_template' for single templates or 'create_template' for creation, nor does it specify prerequisites or exclusions. The agent must infer usage from the name and parameters alone.

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

Related 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/sellersmith/tailorkit-mcp'

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