Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_unused_media

Read-only

Finds uploaded Snapchat ad account images and videos not referenced by any creative or creative element, listed oldest first; read-only and never deletes.

Instructions

Which uploaded images and videos does no creative use? (read-only; never deletes) Oldest first. A file counts as used if any creative or creative element of this ad account mentions it.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

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 description's 'read-only; never deletes' largely restates them. It does add genuine behavioral context the annotations do not: result ordering ('Oldest first') and a precise definition of 'used' that determines inclusion. It still says nothing about pagination, cost, or what a returned record contains.

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?

Three short sentences with the core question front-loaded, followed by the safety note, ordering, and the definition of 'used'. No filler and no repetition.

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 covers the key decision points: what counts as unused, the ordering, the account scope, and that nothing is modified. The outstanding gap is the limit/pagination behavior and the shape of returned media records, which an agent needs to page through results.

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?

The single parameter 'limit' (default 100, max 500) has 0% schema description coverage, so the description must carry its meaning — but it never mentions limit, pagination, or whether results are capped or truncated. The ordering hint ('Oldest first') partially implies which files a limit excludes, but only obliquely.

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 question the tool answers — finding uploaded images and videos that no creative uses — and defines the criterion ('A file counts as used if any creative or creative element of this ad account mentions it'). That distinguishes it from the plain listing siblings like snap_list_media, though it never names them.

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?

The purpose implies the use case (finding cleanup candidates), and 'read-only; never deletes' reassures the agent about consequences, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for actually removing or inspecting media.

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