Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_list_catalogs

Read-only

Retrieve product catalogs for an organization to inspect available catalog data; defaults to the ad account's organization when no ID is provided.

Instructions

List product catalogs of the organization (read-only). Organization id defaults to the ad account's organization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snap_list_catalogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the '(read-only)' parenthetical mostly restates structured data. The one genuinely additive behavioral fact is the default resolution of organization_id to the ad account's organization, but nothing is said about results size, pagination, or ordering.

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?

Two short sentences, front-loaded with the action and resource, with the parameter default immediately after. The '(read-only)' fragment is slightly redundant with the annotations but costs little.

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

Completeness4/5

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

This is a low-complexity read tool with one optional parameter and no output schema, and the description covers the action, scope, and parameter default. Only secondary details such as pagination or result shape are absent, which is acceptable here.

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% for the single optional organization_id parameter, so the description must carry the meaning. It does so by explaining the fallback to the ad account's organization, which is not derivable from the schema's pattern constraint alone.

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 states a specific verb and resource ('List product catalogs of the organization'), so an agent knows exactly what is returned. It does not explicitly differentiate itself from nearby siblings such as snap_list_product_sets or snap_catalog_feed_status, so it stops short of a 5.

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?

Usage is implied by the scoping phrase 'of the organization', and the description clarifies the default organization when the id is omitted, which is a real usage aid. However, there is no explicit when-to-use versus alternatives guidance and no exclusions.

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