Skip to main content
Glama
saadsh0

Snapchat Ads MCP Server

by saadsh0

snapchat_get_campaigns

Read-only

List all campaigns for a Snapchat Ad Account with status and budget info. Returns active, paused, and completed campaigns.

Instructions

List all campaigns for a Snapchat Ad Account with status and budget info. Returns ACTIVE, PAUSED, and COMPLETED campaigns — excludes DELETED only. Results cached for 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only and non-destructive. The description adds that it returns only active, paused, completed campaigns (excluding deleted) and that results are cached for 5 minutes, which goes beyond 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?

Extremely concise: two sentences covering purpose, return details, and caching. No wasted words; every sentence adds value.

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?

Output schema exists. Description adequately covers the main behavior (list, statuses, caching) but could mention pagination or ordering if applicable. Minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not elaborate on the 'ad_account_id' parameter beyond what the schema provides. No additional meaning or usage tips are given, despite low coverage.

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?

Clearly states 'List all campaigns for a Snapchat Ad Account with status and budget info.' Specific verb 'list' and resource 'campaigns' with scope. Also distinguishes that it excludes DELETED campaigns, making it distinct from other sibling tools like snapchat_get_ads.

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 explicit guidance on when to use this tool versus alternatives like snapchat_get_ad_squads or snapchat_get_performance_stats. The description does not mention when not to use it or provide context for selection among siblings.

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/saadsh0/snapchat-ads-mcp'

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