Skip to main content
Glama

list_product_sets

Retrieve product sets from a specified product catalog. Use catalog ID to filter results, with optional fields and pagination.

Instructions

List product sets within a catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalog_idYesProduct catalog ID
fieldsNoComma-separated fields to return
limitNoNumber of results to return
afterNoPagination cursor for next page

Implementation Reference

  • The handler function for the list_product_sets tool. It accepts catalog_id, fields, limit, and after parameters, makes a GET request to /{catalog_id}/product_sets, and returns the JSON response with rate limit info.
      async ({ catalog_id, ...params }) => {
        try {
          const { data, rateLimit } = await client.get(`/${catalog_id}/product_sets`, { ...params });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Zod schema definitions for the list_product_sets tool's input parameters: catalog_id (required string), fields (optional string), limit (optional number, default 25), after (optional string for pagination).
    {
      catalog_id: z.string().describe("Product catalog ID"),
      fields: z.string().optional().describe("Comma-separated fields to return"),
      limit: z.number().optional().default(25).describe("Number of results to return"),
      after: z.string().optional().describe("Pagination cursor for next page"),
    },
  • Registration of the 'list_product_sets' tool via server.tool() within the registerCatalogTools function, which is exported and called from src/index.ts line 71.
    server.tool(
      "list_product_sets",
      "List product sets within a catalog.",
      {
        catalog_id: z.string().describe("Product catalog ID"),
        fields: z.string().optional().describe("Comma-separated fields to return"),
        limit: z.number().optional().default(25).describe("Number of results to return"),
        after: z.string().optional().describe("Pagination cursor for next page"),
      },
      async ({ catalog_id, ...params }) => {
        try {
          const { data, rateLimit } = await client.get(`/${catalog_id}/product_sets`, { ...params });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as read-only nature, pagination handling, or performance characteristics. The description is too minimal to compensate.

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 sentence that is front-loaded and concise, with no unnecessary words.

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?

The description combined with schema provides basic understanding but lacks information on return format, pagination cursor behavior, and differentiation from siblings. No output schema exists, so more context would be beneficial.

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 description adds no additional meaning beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'product sets' within a catalog, which distinguishes it from sibling list tools like list_catalogs or list_products.

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, nor any exclusions or prerequisites beyond the schema's required catalog_id.

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/mikusnuz/meta-ads-mcp'

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