Skip to main content
Glama
get-mcp-ads

Reddit Ads MCP server

reddit get creative assets

reddit_get_creative_assets
Read-onlyIdempotent

List paginated creative assets from a Reddit profile's asset library linked to an ad account, so you can inspect available files and choose assets for ad setups.

Instructions

List the asset library of a profile attached to the ad account; unused files are not necessarily ads.

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 100. Defaults to 50.
cursorNoOpaque next_cursor returned by the previous page. Omit it for the first page.
profileIdYesReddit profile ID (t2_...) attached to adAccountId. List them with reddit_get_profiles.
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. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is covered. The description adds one genuinely useful semantic caveat (library assets ≠ ads) but says nothing about ordering, result volume, or pagination behavior beyond what the schema's limit/cursor fields already convey.

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 compact sentence with the core action front-loaded and no filler. It is efficient, though the semicolon clause packs in a caveat that could be phrased more directly.

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 an output schema, full annotation coverage, and 100% parameter documentation, most of the burden is carried elsewhere. However, for a paginated list tool the description gives no sense of what an 'asset' is (image/video/etc.) or result volume, leaving it minimally adequate rather than complete.

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% and the parameter descriptions are strong — profileId even points to reddit_get_profiles and adAccountId distinguishes the ad account from the business ID. 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 verb and resource: "List the asset library of a profile attached to the ad account." The trailing clause clarifies what the returned items are (raw library files, not necessarily live ads), which meaningfully separates it from ad/creative listings, though no sibling is named explicitly.

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?

Usage is only implied: the note that "unused files are not necessarily ads" hints this is the raw-library lookup rather than an ad/creative listing. It never names reddit_list_ad_creatives or reddit_get_asset_uploads as alternatives, nor states when to prefer one over the other.

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