Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_get_media

Read-only

Reads a media asset and its processing status after an ad code is claimed, so you can confirm readiness before using it in an ad.

Instructions

Get a media asset and its processing status (read-only). Use after claiming an ad code.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_id": "<media_id>"
    },
    "name": "snap_get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYes

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 parenthetical "(read-only)" adds nothing. The one piece of real added context is that the response carries processing status, implying the asset may be asynchronously processed and worth re-polling — a useful behavioral signal, though no retry or timing guidance is given.

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 short sentences, front-loaded with the action and its return content, with the usage hint second. The "(read-only)" parenthetical is redundant with annotations and is the only wasted token.

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 one-parameter lookup with no output schema, the definition covers the essential action and hints at the returned status field. It is incomplete on the two things an agent would most need: what identifies a valid media_id and what to do if processing is still pending.

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?

With a single required parameter and 0% schema description coverage, the description must explain media_id, and it does not — it never states the format, origin, or whether the value comes from snap_claim_ad_code. The only implicit hint is the "after claiming an ad code" sequencing, which is indirect rather than a definition of the parameter.

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?

Names a specific verb and resource ("Get a media asset") and adds that the response includes processing status, which distinguishes it from a bulk lister like snap_list_media by implication of singularity. It stops short of explicitly contrasting with the sibling list tool, so an agent must infer that distinction from the name.

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?

"Use after claiming an ad code" gives a concrete sequencing hint tied to snap_claim_ad_code, which is genuinely useful. However, it never says when not to use it (e.g., versus snap_list_media for enumeration) and leaves ambiguous whether the input is the ad code itself or a separate media identifier returned by the claim step.

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