Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_list_adsquads

Read-only

List ad squads for a campaign or ad account in read-only mode, with optional status and name filters; reads every page and notes when results are truncated.

Instructions

List ad squads for a campaign, or for the whole ad account when only the account is given (read-only). Reads every page and applies the status filter before the limit; 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_adsquads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
campaign_idNo
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavior: it paginates through every page internally, applies the status filter before the limit (so limit is a post-filter cap, not a page size), and annotates the response when the list is truncated. That last point is exactly the kind of disclosure an agent needs and cannot get from annotations.

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?

A single dense sentence that front-loads the primary purpose and appends the operational caveats. No filler, no restating of the tool name, and the pagination/truncation behavior is packed into one clause.

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?

With 5 parameters, 20% schema coverage, and no output schema, the description does well on filtering and truncation semantics but leaves gaps: no rules for the campaign_id/ad_account_id combination, nothing about limit's default or maximum, and no mention of name_contains. An agent could still mis-call it by supplying both ids.

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 only 20% (only name_contains is documented inline), so the description has to compensate. It does clarify the filter-then-limit ordering, but leaves limit's role, the campaign_id vs ad_account_id interaction (what happens when both or neither are supplied), and the status enum values unaddressed.

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?

"List ad squads for a campaign, or for the whole ad account when only the account is given" states a specific verb (list) plus resource (ad squads) and defines the two scoping modes. The resource name alone separates it from snap_list_ads, snap_list_campaigns and snap_list_creatives, so the agent can pick it out without opening the schema.

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?

The description gives clear context for the two invocation shapes: pass a campaign to scope to that campaign, or pass only the account to scope to the whole account. It does not name a sibling or state when NOT to use this tool, which keeps it below a 5.

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