Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Update Meta Placements (Facebook / Instagram)

update_meta_placements
Destructive

Set the channel-level Meta placement default of an existing DRAFT wizard campaign's Facebook or Instagram channel: automatic placements (Meta decides where ads serve) or a manual list of surfaces (Feed, Stories, Reels, ...).

            Placements are where the ads serve inside Meta's networks. This is the same
            "Placements" control the platform UI shows in the Facebook/Instagram section of
            the campaign draft page. The campaign MUST already have the channel enabled
            (via create_campaign / add_and_edit_campaign_elements).

            WARNING: DRAFT-ONLY: the platform rejects the edit once the campaign is Launching/Launched.

            KEYWORDS: meta, facebook, instagram, threads, placements, placement, feed, stories,
            reels, explore, search results, profile feed, automatic placements, manual placements,
            advantage+ placements, where ads serve, surfaces, channel settings, campaign settings

            WHEN TO USE:
            - Serve ads only on specific surfaces (e.g. Instagram Reels and Stories)
            - Switch a channel back to automatic placements (Meta optimizes delivery)
            - The user asks where their Facebook/Instagram ads will appear

            PARAMETERS:
            - campaign_id: the wizard campaign ID (required)
            - channel: FACEBOOK | INSTAGRAM (required — the campaign channel to edit)
            - mode: AUTO | MANUAL (required). AUTO = automatic placements, clears any
              manual set. MANUAL = serve only on the placements listed.
            - placements: array of placement codes, required when mode=MANUAL, ignored
              for AUTO. Facebook surfaces: FB_FEED, FB_STORIES, FB_REELS,
              FB_SEARCH_RESULTS. Instagram surfaces: IG_FEED, IG_PROFILE_FEED,
              IG_EXPLORE, IG_EXPLORE_HOME, IG_STORIES, IG_REELS, IG_SEARCH_RESULTS.
              Threads: TH_THREADS_STREAM.

            PLACEMENT RULES (enforced; violations return a descriptive error):
            - Companion rules: FB_STORIES and FB_SEARCH_RESULTS require FB_FEED;
              IG_PROFILE_FEED, IG_SEARCH_RESULTS and IG_EXPLORE require IG_FEED;
              IG_EXPLORE_HOME requires IG_EXPLORE; TH_THREADS_STREAM requires IG_FEED.
            - An INSTAGRAM channel accepts IG_* placements only.
            - A FACEBOOK channel always accepts FB_* placements. IG_* / TH_* placements
              on a FACEBOOK channel additionally need the account's unified-placement
              rollout (feature flag CORE_META_IG_PLACEMENT_ON_FB) — the platform rejects
              them on accounts without it.
            - IG_PROFILE_FEED is not available on Lead Gen (CPL) campaigns.
            - AUTO is rejected while the channel has ad groups (per-ad-group setups keep
              manual placements).

            This tool sets the campaign-wide default for the channel. Per-ad-group
            placement overrides exist in the platform UI but are not editable through
            chat yet — send users to the campaign page for per-ad-group customization.

            EXAMPLES:

            Instagram channel, Reels + Stories + Feed only:
            update_meta_placements({"campaign_id": 12345, "channel": "INSTAGRAM",
                "mode": "MANUAL", "placements": ["IG_FEED", "IG_STORIES", "IG_REELS"]})

            Facebook channel back to automatic placements:
            update_meta_placements({"campaign_id": 12345, "channel": "FACEBOOK", "mode": "AUTO"})

            RESPONSE: {success, campaign_id, channel_id, channel, campaign_status,
            applied:{mode, placements}, previous?, errors?}
            `previous` echoes the channel's placement state before the edit.

            INTEGRATION WITH OTHER TOOLS:
            - Use search_campaigns_by_names / get_campaign_by_wizard_id to find the campaign
            - The channel is enabled by create_campaign or add_and_edit_campaign_elements
            - Reddit placements (feed/conversations) are a different system: use
              update_reddit_channel_settings for those

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesAUTO = automatic placements (Meta decides, clears the manual set). MANUAL = serve only on the placements listed in `placements`.
channelYesWhich campaign channel to edit. Meta placements only exist on Facebook and Instagram channels.
placementsNoPlacement codes to serve on. Required when mode=MANUAL (at least one); ignored for AUTO. Companion rules apply — see the tool description.
campaign_idYesThe unique identifier of the wizard campaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond that: it warns DRAFT-ONLY with platform rejection, explains AUTO clears any manual set, documents enforced placement rules with companion requirements, notes IG_PROFILE_FEED unavailability on Lead Gen, and states AUTO is rejected while the channel has ad groups. It also discloses the response shape including `previous` and `errors?`. No contradiction with 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?

The description is long but every section earns its place: purpose, keywords, when-to-use, parameters, placement rules, examples, response, and integration. It is well-structured with clear headers and front-loaded with the core purpose. It loses one point because the keyword list is somewhat redundant and the overall length is high, though the density of useful information justifies most of it.

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 complex mutation tool with 4 parameters, enforced business rules, and no output schema, the description is remarkably complete. It covers prerequisites, constraints, placement rules, examples, response format, and integration with other tools. An agent has everything needed to select and invoke this tool correctly, including edge cases like the unified-placement rollout and per-ad-group limitations.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning beyond the schema: it explains the semantic difference between AUTO and MANUAL (AUTO clears manual set), lists exact placement codes per surface, documents companion rules, channel-specific restrictions, the unified-placement rollout flag, and the Lead Gen exception. It also clarifies that `placements` is ignored for AUTO. This far exceeds what the schema provides.

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 description states a specific verb ('Set'), a specific resource ('channel-level Meta placement default of an existing DRAFT wizard campaign's Facebook or Instagram channel'), and the two modes (automatic vs manual list of surfaces). It clearly distinguishes this from sibling tools like update_reddit_channel_settings and update_linkedin_channel_settings by naming them and noting Reddit placements are a different system.

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 has an explicit 'WHEN TO USE' section listing concrete scenarios (serve ads only on specific surfaces, switch back to automatic placements, user asks where ads will appear). It also states when NOT to use it: DRAFT-ONLY, rejected once Launching/Launched, and per-ad-group overrides are not editable through chat. It names alternatives (update_reddit_channel_settings) and prerequisite tools (create_campaign / add_and_edit_campaign_elements).

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 toolsInspect
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