Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_report_async_download

Idempotent

Downloads a completed Snapchat async report as a CSV into the project's exports/ folder and returns the file path and row count.

Instructions

Download a COMPLETED async report as a CSV into this project's exports/ folder and return its path and row count. Reads from Snap only; writes one local file.

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": {
      "entity": "<entity>",
      "id": "<id>",
      "report_run_id": "<report_run_id>"
    },
    "name": "snap_report_async_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
file_nameNo
report_run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false; the description adds genuine context beyond that by clarifying the write is only a single local file ('writes one local file') and that no Snap state is mutated ('Reads from Snap only'). It doesn't say whether an existing file is overwritten or how large a report may be, but the side-effect profile is clear.

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 short sentences, front-loaded with the action and destination, followed by a compact statement of the read/write boundary. No filler.

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?

With no output schema, the description usefully states the return values (path and row count) and the completion precondition. However, for a four-parameter tool with zero schema coverage, the meanings of entity/id/report_run_id remain unexplained, leaving a meaningful gap for correct invocation.

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% across four parameters, and the description explains none of them: neither 'entity' nor 'id' nor 'report_run_id' nor 'file_name' is defined, and the enum values (adaccount/campaign/adsquad/ad) go unmentioned. Only indirectly does 'COMPLETED async report' hint at report_run_id; the description does not compensate for the coverage 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?

States a specific verb ('Download'), a specific resource ('a COMPLETED async report'), the output format (CSV), and the destination ('this project's exports/ folder'). This clearly distinguishes it from snap_report_async_start and snap_report_async_status, which handle the other stages of the async workflow.

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?

The capitalized 'COMPLETED' makes the precondition explicit: call this only after the async run has finished, implying the agent should check snap_report_async_status first. It doesn't name an alternative for unfinished reports or state what happens if the run is still pending, so it falls short of a full when/when-not/alternatives treatment.

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