Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_list_product_sets

Read-only

Lists all product sets in a specified catalog so you can review and audit catalog organization without making changes.

Instructions

List product sets of a catalog (read-only).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "catalog_id": "<catalog_id>"
    },
    "name": "snap_list_product_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
catalog_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the parenthetical "(read-only)" adds nothing beyond structured data. The description is silent on the behaviors that openWorldHint raises — result volume, pagination, or ordering — which would have been genuinely useful extra context.

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?

One short sentence with the resource front-loaded and no filler. It is efficient, though the brevity is partly the cause of the missing guidance rather than purely a virtue.

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?

For a simple one-parameter read tool with no output schema, the definition covers the basic action but leaves the return shape and list-size/pagination expectations unstated, which matters for an open-world listing tool. Adequate, not complete.

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?

There is a single required parameter with 0% schema description coverage, so the description has to carry the load; it only implies that catalog_id is the parent catalog identifier. The self-explanatory name and the schema's pattern constraint keep this minimally viable, but no format, ID source, or example is given.

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 names a specific verb and resource ("List product sets") and scopes it to a parent catalog, which cleanly separates it from the create-side sibling snap_create_product_set and from snap_list_catalogs. It does not differentiate against the many other snap_list_* siblings, but the resource noun is distinctive enough to route correctly.

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 when-to-use or when-not-to-use guidance is offered, and no alternative is named. The only implicit cue is that a catalog context is required, which an agent could infer from the parameter anyway.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools