Metadata MCP Connector

Check Campaign Launch Readiness

check_campaign_launch_readiness

Read-only

Check whether a draft campaign is ready to launch, per channel. Reads the campaign's real configuration from the platform and reports, for each ENABLED channel, whether it has the ads, audience, offer, budget AND a live channel connection it needs to go live - plus a specific list of blockers for anything missing.

            Enabled Facebook/Instagram VIDEO creatives must contain a usable saved
            Meta video_id in their creative JSON. A later library upload becoming
            READY does not heal a creative saved without it; rebuild/update the ad
            after upload completion, refresh the campaign creative, then recheck.
            launch_campaign repeats this observed video check before any ad completion.

            KEYWORDS: campaign, launch, readiness, ready, preflight, can launch, blockers, missing, go live, validate, checklist

            WHEN TO USE:
            - Before launching a campaign, to confirm it is actually ready
            - After assembling or editing a draft, as the go/no-go check
            - When the user asks "is my campaign ready to launch?" or "what's missing?"

            RETURNS:
            A per-channel readiness report:
            - is_launchable: whether EVERY enabled channel is ready
            - verified: whether the platform's pre-launch check actually answered. When false,
              is_launchable is an assumption, NOT a verdict - say the check could not be run
              instead of telling the user the campaign is ready.
            - channels: [{channel, launchable, blockers[], ads, audiences, offers, budget}]
            - summary: a one-line human verdict
            This is a READ-ONLY check - it does NOT launch anything. Use launch_campaign to actually launch.

            CHANNEL CONNECTION: a channel with no live integration is reported as a blocker here, and the
            platform will refuse the launch itself. This is the ONLY point in a build where a missing
            connection matters - audiences, targeting, offers, creative and the draft campaign are all
            built without one on purpose. So do NOT ask the user to connect anything earlier; raise it
            here, name the channels, and offer to connect them.

            PARAMETERS:
            - campaign_id: The wizard campaign ID (integer, required)

            CAMPAIGN ID SOURCES:
            - search_campaigns_by_names tool (returns campaign IDs)
            - create_campaign tool response (returns campaign_id)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaign_id`	Yes	The wizard campaign ID to check launch readiness for

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?

Annotations already establish read-only safety, but the description adds substantial non-obvious behavior: the meaning of the 'verified' flag (false means is_launchable is an assumption, not a verdict), the channel-connection blocker semantics and the instruction not to raise connections earlier, and the video_id gotcha where a later library upload does not heal a saved creative. This is rich context an agent could not infer from the annotations.

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?

Purpose and the crucial caveats are front-loaded, and the sectioned layout (RETURNS, CHANNEL CONNECTION, PARAMETERS) is easy to scan. The KEYWORDS line and some repetition around the video check add bulk that doesn't strictly earn its place, 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.

Completeness5/5

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

Although there is no output schema, the description fully enumerates the return shape (is_launchable, verified, channels[], summary) and the per-channel fields, and it covers the failure mode when the platform check cannot be run. An agent has everything needed to call it and interpret the result.

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% for the single campaign_id parameter, so the baseline is 3. The description adds practical value by naming where to obtain the ID (search_campaigns_by_names, create_campaign response), which is beyond the schema's type/description.

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?

States a specific verb and resource ('Check whether a draft campaign is ready to launch, per channel') and immediately frames the scope as a read-only preflight. It explicitly distinguishes itself from launch_campaign, so an agent can separate the check from the action without opening either schema.

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?

Contains a dedicated WHEN TO USE block with three concrete triggers, including the user phrasing 'is my campaign ready to launch?'. It also names the alternative (launch_campaign) and states that this tool does not launch anything, so the when-to-use boundary is explicit.

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?