Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_list_media

Read-only

List images and videos in an ad account, newest first, to find media IDs for creative creation; filter by type or name, with read-only access and ready-only results by default.

Instructions

List the images and videos in the ad account (read-only), newest first, to find a media_id for snap_create_creative, snap_create_story_creative or snap_create_collection_creative. By default only READY media; filter by type and name. Reads every page; 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_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
ready_onlyNo
ad_account_idNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds real behavior: results are newest-first, the default filter is READY-only, the tool reads every page rather than one page, and it emits a note when the list is truncated. Pagination and truncation disclosure are exactly the kind of operational detail annotations cannot convey.

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 with the core action and scope front-loaded, followed by defaults/filters and pagination behavior. Every clause carries information: consumer tools, ordering, filter defaults, and truncation notice.

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 usefully describes the return shape at a high level (a newest-first media list usable for media_id, plus a truncation note). It leaves the exact fields per media item and the meaning of limit unstated, but the essential facts needed to call it correctly are present.

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 description coverage is 0%, so the description must carry parameter meaning: it explains the type filter, the name filter, and the READY-only default that maps to ready_only. The limit and ad_account_id parameters are only weakly implied ('in the ad account', 'reads every page'), 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 gives a specific verb and resource ('List the images and videos in the ad account'), states ordering ('newest first'), and names the downstream consumers (snap_create_creative, snap_create_story_creative, snap_create_collection_creative) whose media_id it supplies. An agent can distinguish this from snap_get_media or snap_unused_media based on the stated intent.

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 clearly frames the use case (finding a media_id for creative creation) and states the default behavior (READY only) plus the filtering options by type and name. It does not explicitly exclude or compare against siblings like snap_get_media or snap_unused_media, so it stops short of full when-not guidance.

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