Skip to main content
Glama

Metadata MCP Connector

Create or Update Image Ad

create_update_image_ad
Destructive

Create OR update an IMAGE (or GIF, except on X) ad on Facebook, Instagram, LinkedIn, Reddit, and/or X. TO UPDATE: include id; to CREATE: omit it. An X ad that belongs to a launched campaign cannot be updated.

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": {
      "ads_data": "<ads_data>"
    },
    "name": "create_update_image_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ads_dataYesArray of IMAGE ads to create or update. Each item targets one or more of FB/IG/LinkedIn/Reddit/X; the platform creates one ad row per (ad, channel).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / ads_data / description
      Previous value: -"Array of IMAGE ads to create or update. Each item targets one or more of FB/IG/LinkedIn/Reddit; the platform creates one ad row per (ad, channel)."New value: +"Array of IMAGE ads to create or update. Each item targets one or more of FB/IG/LinkedIn/Reddit/X; the platform creates one ad row per (ad, channel)."
    • changedInput schema / properties / ads_data / items / properties / channels / description
      Previous value: -"Target channels. Each channel produces one ad row (an ad targeting two channels yields two ads)."New value: +"Target channels. Each channel produces one ad row (an ad targeting two channels yields two ads). X (Twitter) ads are promoted posts with a website card, IMAGE ads only: a PNG or JPG, not a GIF (the platform UI says X promoted posts do not support GIFs), ideally 1.91:1 (1200x628) or 1:1 (800x800), up to 5 MB. X cards have no call-to-action button. An X ad's name gets an _X suffix, as LinkedIn and Meta names get _LI, _FB and _IG, and becomes the card's name on X."
    • changedInput schema / properties / ads_data / items / properties / channels / items / enum
      Previous value: -[
      -  "Facebook",
      -  "Instagram",
      -  "LinkedIn",
      -  "Reddit"
      -]New value: +[
      +  "Facebook",
      +  "Instagram",
      +  "LinkedIn",
      +  "Reddit",
      +  "X"
      +]
    • addedInput schema / properties / ads_data / items / properties / xDisplayURL
      Added value: +{
      +  "description": "Display URL for X ads. Required for X. MUST start with http:// or https://, even on IMAGE ads. Max 2000 chars. The card itself clicks through to the landing page offer of the campaign the ad runs in (plus its UTMs), not to this URL.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • addedInput schema / properties / ads_data / items / properties / xHeadline
      Added value: +{
      +  "description": "Website card headline for X ads. Required for X. Max 280.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
    • addedInput schema / properties / ads_data / items / properties / xText
      Added value: +{
      +  "description": "Optional post text shown above the X card, max 280 characters (the platform's limit for it); when empty X posts the headline as the text.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare that this is non-read-only, destructive, and open-world. The description adds useful constraints around updates and GIF support on X, but it does not explain what an update overwrites or how destructive changes affect existing ads.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with the primary purpose and create/update rule front-loaded. Every sentence adds relevant scope or constraint information without repetition.

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

Completeness4/5

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

Given the rich schema and safety annotations, the description is sufficient for selecting and invoking the tool. It does not state what creation returns, and with no output schema that is a minor completeness gap for a tool that creates ads.

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 nested fields already document required values, limits, and channel-specific behavior. The description only restates the `id` include/omit rule for create versus update, so it does not add much beyond the schema.

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 pair and resource: create or update an IMAGE/GIF ad across named channels. The create-vs-update rule using `id` is explicit, and the image/GIF scope distinguishes it from sibling ad-format tools such as video, carousel, and document ads.

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

Usage Guidelines4/5

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

It gives a clear operational condition: include `id` to update and omit it to create. It also states a meaningful exclusion for X ads tied to launched campaigns, though it does not explicitly route users to sibling tools for other ad formats.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources