Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upload creative assets

reddit_ads_upload_creative_assets

Add up to 50 images, videos, headlines, or CTAs to a Reddit Ads profile's creative library from public URLs, then poll for upload status.

Instructions

Add up to 50 assets to a profile's creative library (used by Reddit Max ads). Media is fetched by Reddit from public URLs. Poll reddit_ads_get_creative_asset_upload for the resulting asset.

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": {
      "profile_id": "<profile_id>",
      "data": "<data>"
    },
    "name": "reddit_ads_upload_creative_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesSent as {"data": [...]}. Items: {type: "IMAGE", name, media: {type: "URL", url}}, {type: "VIDEO", name, media: {type: "URL", url}, poster: {type: "URL", url}}, {type: "HEADLINE", text}, {type: "CTA", call_to_action}; each may have reference_id. call_to_action values: Apply Now, Contact Us, Download, Get a Quote, Get Showtimes, Install, Learn More, Order Now, Play Now, Pre-order Now, See Menu, Shop Now, Sign Up, View More, Watch Now, Book Now, Buy Tickets, Get Directions, Listen Now, Read More, Subscribe, Visit Store, Donate Now, Remind Me.
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive mutation in an open-world API. The description adds genuinely new behavior: the 50-asset cap, that Reddit fetches media from public URLs (so URLs must be publicly reachable), and that the operation is asynchronous and requires polling a separate tool. The async/polling disclosure is the most valuable piece and is not derivable from annotations.

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 tight sentences with the core action front-loaded, followed by two distinct operational facts (public URLs, polling). No filler; each sentence earns its place.

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?

For a no-output-schema async mutation, the description covers the essentials: caps, media source constraints, and how to retrieve the result. It lacks any note on auth/permission requirements for the target profile, which would fully close the gap.

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?

Schema coverage is 50%: the data parameter carries a very rich inline description (item types, call_to_action enum values), while profile_id is undocumented in both places. The description reinforces the 50-item limit and the public-URL requirement, but adds little beyond what the schema already states. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Add up to 50 assets to a profile's creative library', plus the Reddit Max ads context. This is clearly distinguishable from the sibling list/get/update/delete creative asset tools. It stops short of explicitly naming which sibling it is not, so it's a clear-but-not-differentiating 4.

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?

Provides useful follow-up routing ('Poll reddit_ads_get_creative_asset_upload for the resulting asset') and scopes to Reddit Max ads. However, it gives no when-to-use/when-not guidance versus alternatives like reddit_ads_create_poster_job or why an agent would upload here rather than via another path. Implied usage only.

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