Metadata MCP Connector

Create or Update Reddit Carousel Ad

create_update_carousel_ad

Destructive

Create OR update a CAROUSEL ad on Reddit (Reddit only). TO UPDATE: include id; to CREATE: omit it.

                            A carousel is a SINGLE ad with 2 to 6 swipeable cards. Each card is an
                            image with its own optional CTA; the headline is shared across the whole ad.

                            CREATIVE WORKFLOW:
                              1. Upload each card image via `upload_image_creative` -> response gives `id` (the imageLibraryId).
                              2. Pass those ids as cards[].imageLibraryId here (2 to 6 cards, no duplicate images).
                              3. Optionally upload a separate thumbnail image and pass its id as thumbnailLibraryId.

                            ALSO KNOWN AS: create carousel ad, update carousel ad, edit carousel ad,
                            modify carousel ad, multi-image ad, swipeable ad, Reddit carousel.

                            CLIENT-SIDE VALIDATION (mirrors what the platform UI rejects):
                              - adName: required, max 50 chars.
                              - headline: required, max 300 (shared across all cards).
                              - cards: 2 to 6 items; each needs imageLibraryId; no duplicate images.
                              - cards[].cta: optional, must be a valid Reddit CTA enum.
                              - text: optional body, max 2000.
                              - thumbnailLibraryId: optional.

                            REDDIT CTA VALUES: Apply Now, Contact Us, Download, Get a Quote, Learn More,
                            Play Now, Sign Up, View More, Watch Now, Book Now, Listen Now, Read More, Subscribe.

                            See `create_update_image_ad` / `create_update_video_ad` for single-creative Reddit ads.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Include to UPDATE an existing carousel ad; omit to CREATE.
`text`	No	Optional body text. Max 2000.
`cards`	Yes	2 to 6 carousel cards. Each card needs a distinct image (no duplicates).
`adName`	Yes	Ad name. Required, max 50 chars.
`headline`	Yes	Headline shared across all cards. Required, max 300.
`completionStatus`	No	DRAFT (default) persists locally without publishing; COMPLETED finalizes the ad.
`thumbnailLibraryId`	No	Optional thumbnail image library id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint, readOnlyHint), the description adds substantial context: it explains the carousel structure (2-6 cards), the requirement that cards have distinct images, the shared headline, and the DRAFT vs COMPLETED persistence semantics. It also states the validation rules mirror the platform UI, which is valuable behavioral insight.

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?

The description is long but well-organized with clear sections (workflow, validation, CTA values, sibling reference). However, the Reddit CTA values are duplicated in the schema enum, adding redundancy. Everything else earns its place, and the critical information (create/update rule, workflow) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters and no output schema, the description is complete: it covers prerequisites (image upload), constraints (card count, no duplicates), enum values, create/update behavior, and alternatives. An agent has everything needed to invoke it correctly without external lookups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds workflow meaning: it explains that `imageLibraryId` comes from `upload_image_creative`, that `headline` is shared across all cards, and that `thumbnailLibraryId` is optional. This goes beyond the schema descriptions by connecting the parameters to a real sequence of actions.

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?

The first sentence states 'Create OR update a CAROUSEL ad on Reddit (Reddit only)' with a clear verb, resource, and platform restriction. It explicitly distinguishes create vs update via the `id` field, and the closing reference to `create_update_image_ad`/`create_update_video_ad` differentiates it from sibling single-creative tools.

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

Usage Guidelines5/5

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

The description explicitly says 'TO UPDATE: include `id`; to CREATE: omit it,' giving a direct conditional for use. It also instructs to upload images first via `upload_image_creative` and then pass the resulting ids, and points to sibling tools for single-creative ads, making the decision boundary clear.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?