Skip to main content
Glama
Reddit Ads MCP server

Reddit Ads MCP server

by get-mcp-ads

reddit get asset uploads

reddit_get_asset_uploads
Read-onlyIdempotent

Poll creative asset import uploads for a Reddit profile to check processing status; ACTIVE means media is ready, not that ads are delivering.

Instructions

Poll processing of creative imports through the profile; ACTIVE is media-ready, not advertising delivery.

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": {
      "adAccountId": "<adAccountId>",
      "profileId": "<profileId>",
      "uploadIds": "<uploadIds>"
    },
    "name": "reddit_get_asset_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileIdYesReddit profile ID (t2_...) attached to adAccountId. List them with reddit_get_profiles.
uploadIdsYesUpload IDs returned by reddit_upload_creative_assets, 1 to 50.
adAccountIdYesReddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The clause "ACTIVE is media-ready, not advertising delivery" adds genuine domain semantics beyond the readOnly/idempotent annotations — it prevents an agent from misreporting upload success as ad delivery readiness. However, it says nothing about other terminal statuses (failed, rejected), expected processing latency, or polling cadence, which are the behaviors an agent most needs for a polling tool.

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?

A single front-loaded clause with no filler; the operation is stated before the ACTIVE caveat. The phrase "through the profile" is slightly awkward phrasing rather than waste, keeping it just short of a 5.

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?

An output schema exists, so return values are covered, and annotations cover the safety profile. What remains missing is polling lifecycle guidance — terminal statuses, backoff, and what to do with a batch of up to 50 upload IDs — which is material for a tool whose entire purpose is polling.

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 description coverage is 100%: profileId, adAccountId, and uploadIds all carry inline descriptions including the 1–50 array bound and the cross-reference to reddit_upload_creative_assets. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 action (poll processing status of creative imports) tied to a specific resource (uploads scoped through profileId), which is distinguishable from read-only listing tools like reddit_get_creative_assets. It does not name any sibling tool or explicitly contrast itself with reddit_get_creative_assets, so the differentiation is inferable rather than stated.

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?

"Poll processing" implies usage after reddit_upload_creative_assets (which the schema references for uploadIds), so the calling context is inferable. There is no explicit guidance on when to call it versus reddit_get_creative_assets, how often to poll, or when to stop polling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.