reddit-ads-mcp

Overview Schema Source Related Servers Discussions Admin

List creative asset uploads

reddit_ads_list_creative_asset_uploads

Read-only

Retrieve the status of multiple Reddit Ads creative asset uploads by profile ID and upload IDs, so you can track processing progress and verify results.

Instructions

Get the status of several creative asset uploads.

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>",
      "id": "<id>"
    },
    "name": "reddit_ads_list_creative_asset_uploads"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Upload IDs
`profile_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 29, 2026

TDQS

B3.2/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 safety profile is covered. The description adds that the call returns upload status, which is the key behavioral fact for a status-polling endpoint, but says nothing about authentication scope, per-upload failure semantics, or how partial results behave.

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 sentence with zero filler, but it is arguably too terse for a tool that lacks an output schema, so it stops just short of ideal efficiency.

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 simple read-only batch-lookup tool whose annotations cover safety, the minimal description is close to adequate. However, with no output schema and an undocumented profile_id, the description should at least sketch what 'status' contains or how many uploads can be queried.

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 id array is documented (Upload IDs, max 100/min 1) while profile_id is undocumented in both places. The description's 'several' reinforces the batch nature of the id array but does not compensate for the missing profile_id semantics.

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 (get status of creative asset uploads), which is clearly distinct from the singular sibling reddit_ads_get_creative_asset_upload. It does not explicitly contrast itself with that sibling, but the plural/batch nature is discernible from the name and the word 'several'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus the singular get_creative_asset_upload, and no mention of prerequisites, polling cadence, or when a batch status check is preferable. The agent must infer usage from the name alone.

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

Deploy Server