Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_list_campaigns

Read-only

Lists campaigns in a Snapchat ad account with status and name filters, reading every page before applying limits so you can locate a specific campaign in a large account.

Instructions

List campaigns in an ad account (read-only). Uses SNAP_AD_ACCOUNT_ID if no account is given. Reads every page and applies the status and name_contains filters before the limit (use name_contains to find one campaign in a big account); a note says when the list is cut.

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_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
ad_account_idNo
name_containsNoOnly items whose name contains this text (case-insensitive). Use it to find one item in a big account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.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 safety is covered. The description adds genuine beyond-schema behavior: it reads every page, applies status/name_contains filters before the limit, and returns a note when the list is truncated. However it says nothing about auth requirements, error behavior, or result ordering, so it is useful but not rich.

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?

Two dense sentences front-load the operation and read-only nature, then cover defaulting, filtering order, and truncation. Nothing is redundant and no sentence is wasted.

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?

With no output schema, the description still explains that results span all pages and that a truncation note appears when the limit cuts the list, which is the key return-value caveat for a paginated list tool. Minor omissions such as ordering and page size are not blocking for correct invocation.

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 coverage is only 25% (just name_contains is documented), so the description must compensate, and it largely does: it explains the ad_account_id fallback, the effect of status and name_contains on results, and that limit applies after filtering. It never clarifies the meaning of the limit default or status values beyond the enum, leaving a small gap.

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 names a specific verb and resource ('List campaigns in an ad account') and tags it as read-only. The resource noun ('campaigns') is what separates it from sibling list tools such as snap_list_ads and snap_list_adsquads, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operational guidance: the account falls back to SNAP_AD_ACCOUNT_ID when omitted, and name_contains is the recommended way to locate a single campaign in a large account. It does not state when to prefer a different sibling tool, but no direct alternative for listing campaigns is evident.

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