Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_review_issues

Read-only

Identify rejected or pending Snapchat ads and retrieve Snap's review reasons, filtered by default to active ad squads to audit approval issues.

Instructions

Ads that are rejected or pending review, with Snap's reasons (read-only). By default only ads whose ad squad is ACTIVE.

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

Input Schema

NameRequiredDescriptionDefault
only_activeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.4/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 '(read-only)' note largely restates structured data. The genuinely additive behavior disclosure is the default ACTIVE ad-squad scoping, but nothing is said about result size, pagination, or how long rejected ads remain visible.

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 tight sentences with the core purpose front-loaded and no filler. The trailing default-filter clause is slightly compressed in phrasing but still earns its place by clarifying scope.

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 single-parameter read tool with no output schema, the description covers the essentials: what is returned and the default scope. It falls short on the false case for the only parameter and on result-shape hints beyond 'with Snap's reasons'.

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 one parameter with 0% schema description coverage, so the description must carry the meaning. It does explain the default semantics of the active-only filter, but never states what passing false returns (e.g., rejected ads in paused or archived squads), leaving the agent to infer the toggle's effect.

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 resource and filter: ads that are rejected or pending review, returned with Snap's review reasons. That is enough for an agent to tell it apart from sibling diagnostic tools such as snap_anomaly_check or snap_ad_preview, though the verb (list/retrieve) is only implied rather than stated.

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?

It gives one usage-relevant default (only ads whose ad squad is ACTIVE), which tells the agent what to expect without extra input. It never says when to set only_active=false or when to prefer another tool for ad status questions, so the when-to-use guidance is implied rather than explicit.

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