Skip to main content
Glama

Launch brief

launch_brief

Prepares or continues a Meta launch brief. userStatement carries the user's request or answer for this launch in their own words, and input carries only confirmed choices. Returns the open questions with their labels and named options, and maps names only to IDs it supplied; each call with new answers updates the brief. The account, budget and launch mode come from the person, not from defaults. A Leads launch on an instant form takes the form's id from userStatement or from metaSettings.ad.leadFormId; targeting_options kind=lead-form lists a Page's forms. A completed brief goes to campaigns_launch, which returns an Adrails approval link: nothing goes live or spends without approval in the browser.

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": {
      "input": "<input>",
      "userStatement": "<userStatement>"
    },
    "name": "launch_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementYesThe user's request or answer for this launch, in their own words. Required: no Adrails card exists in MCP.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / input / properties / metaSettings / description
      Previous value: -"Every other editor setting the person asked for: several primary texts or headlines for the same ads (variations), cities, regions, radius, postal codes, excluded places, detailed targeting, destinations, budgets, category. Read editor_settings_reference first, and pass only what was asked."New value: +"Every other editor setting the person asked for: several primary texts or headlines for the same ads (variations), cities, regions, radius, postal codes, excluded places, detailed targeting, destinations, an instant form, budgets, category. Read editor_settings_reference first, and pass only what was asked."
  2. Changed3 schema fields changed
    • changedInput schema / properties / input / properties / adPerFile / description
      Previous value: -"True when the person wants each file its own ad (\"1 ad = 1 file\", no carousel): files are never grouped by shape, and each ad is named \"<file without extension> - <subfolder>\"."New value: +"True when the person wants each file its own ad (\"1 ad = 1 file\", no carousel): never grouped by shape, each named \"<file> - <subfolder>\"."
    • changedInput schema / properties / input / properties / objective / enum
      Previous value: -[
      -  "Sales",
      -  "Traffic",
      -  "Leads",
      -  "Engagement"
      -]New value: +[
      +  "Sales",
      +  "Traffic",
      +  "Leads",
      +  "Engagement",
      +  "Awareness",
      +  "App promotion"
      +]
    • changedInput schema / properties / input / properties / urlParameters / description
      Previous value: -"The URL parameters the person gave, Ads Manager's field of that name, without the leading ?: utm_source=facebook&utm_campaign={{campaign.name}}. A destination link that carries UTM fields is split by Adrails on its own."New value: +"The URL parameters the person gave, without the leading ?: utm_source=facebook&utm_campaign={{campaign.name}}. A destination link that carries UTM fields is split by Adrails on its own."
  3. Changed2 schema fields changed
    • changedInput schema / properties / input / properties / objective / enum
      Previous value: -[
      -  "Sales",
      -  "Traffic",
      -  "Leads"
      -]New value: +[
      +  "Sales",
      +  "Traffic",
      +  "Leads",
      +  "Engagement"
      +]
    • changedInput schema / properties / input / properties / source / description
      Previous value: -"Where the creatives are, when the person said or it is plain: a mentioned folder, attached images. none only when the person said they will add the creatives later: the rest is then saved as a draft in Campaigns. posts: existing Page posts are the ads (metaSettings.ad.existingPosts), as a draft too. When they have not said where the creatives are, omit it: the card asks."New value: +"Where the creatives are, when the person said or it is plain: a mentioned folder, attached images. none only when the person said they will add the creatives later: the rest is then saved as a draft in Campaigns. posts: boost existing posts (metaSettings.ad.existingPosts). When they have not said where the creatives are, omit it: the card asks."
  4. Changed25 schema fields changed
    • addedInput schema / properties / input / properties / adSetGroups
      Added value: +{
      +  "additionalProperties": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "description": "One new ad set per group, in one call: {C1:[a,b]}, by file names or a shared code. Then omit creativeNames.",
      +  "type": "object"
      +}
    • changedInput schema / properties / input / properties / beneficiary / description
      Previous value: -"Who benefits from and pays for ads shown in the EU, as stated in the request or earlier turns."New value: +"Who benefits from and pays for ads shown in the EU, as stated."
    • changedInput schema / properties / input / properties / bidAmount / maximum
      Previous value: -1000000New value: +100000000000
    • changedInput schema / properties / input / properties / campaignOnly / description
      Previous value: -"True when the person asks for the campaign alone, with no ad set and no ad. Then nothing about creatives, ad sets or ads is asked."New value: +"True only when the person says they want the campaign alone, with no ad set and no ad. \"Set up a new campaign\" is a launch with ads, not this. Then nothing about creatives, ad sets or ads is asked."
    • changedInput schema / properties / input / properties / conversionEvent / description
      Previous value: -"Use the value stated in the current request or earlier turns, including a name that can be resolved against account facts."New value: +"As stated; a name is resolved against the account."
    • changedInput schema / properties / input / properties / copyMode / description
      Previous value: -"As stated in the request or earlier turns: one copy for every ad, or server-generated copy per ad in batches. Never write more than 25 ad copies in one answer."New value: +"As stated: one copy for every ad, or server-generated copy per ad in batches. Never write more than 25 ad copies in one answer."
    • changedInput schema / properties / input / properties / creativeCount / description
      Previous value: -"How many of the Drive folder's creatives to launch when the person gave a number (\"3 creatives\", \"5 visuels\"): Adrails picks that many from the folder's inventory. Never launch the whole folder when a number was given."New value: +"How many of the Drive folder's creatives to launch (\"3 creatives\", \"5 visuels\"): Adrails picks that many from its inventory. Never the whole folder when a number was given."
    • changedInput schema / properties / input / properties / creativeNames / description
      Previous value: -"The folder's files the person named, by name as they wrote them, when they named which ones."New value: +"The folder's files the person named, as they wrote them."
    • changedInput schema / properties / input / properties / dailyBudget / maximum
      Previous value: -1000000New value: +100000000000
    • changedInput schema / properties / input / properties / formats / description
      Previous value: -"Use the preference stated in the request or earlier turns. Omit to use the server default."New value: +"As stated; omit for the server default."
    • changedInput schema / properties / input / properties / imageUrls / description
      Previous value: -"Public HTTPS image URLs explicitly supplied as creatives in the request or earlier turns. These are creatives, not destination links. Files attached to the message are used on their own: never list them here."New value: +"Public HTTPS image URLs the person gave as creatives, not destination links. Attached files are used on their own: never list them here."
    • changedInput schema / properties / input / properties / layout / description
      Previous value: -"Use the value stated in the current request or earlier turns, including a name that can be resolved against account facts."New value: +"As stated."
    • changedInput schema / properties / input / properties / layout / enum
      Previous value: -[
      -  "one_ad_set",
      -  "ad_set_per_ad",
      -  "campaign_per_ad"
      -]New value: +[
      +  "one_ad_set",
      +  "ad_set_per_ad",
      +  "campaign_per_ad",
      +  "ad_set_per_folder"
      +]
    • changedInput schema / properties / input / properties / onlyFolders / description
      Previous value: -"Only these subfolders of the Drive folder, by name, when the person named some: the other subfolders and the files beside them are left out. With subfolders of one shared folder, folderId is that shared folder."New value: +"Only these subfolders of the Drive folder, by name: the others and the files beside them are left out. With subfolders of one shared folder, folderId is that shared folder."
    • changedInput schema / properties / input / properties / pageId / description
      Previous value: -"Use the value stated in the current request or earlier turns, including a name that can be resolved against account facts."New value: +"As stated; a name is resolved against the account."
    • changedInput schema / properties / input / properties / pixelId / description
      Previous value: -"Use the value stated in the current request or earlier turns, including a name that can be resolved against account facts."New value: +"As stated; a name is resolved against the account."
    • changedInput schema / properties / input / properties / placements / description
      Previous value: -"Manual placements the person named (Instagram Reels, Facebook feed, Stories...). Omit for Advantage+ placements."New value: +"Manual placements the person named (Instagram Reels, Facebook feed, Stories, 9:16...). Omit for Advantage+ placements."
    • changedInput schema / properties / input / properties / publishAs / description
      Previous value: -"How the launch ends: draft in Adrails, paused on Meta, or live only after the person explicitly chooses live in the launch card. A typed live request is a suggestion; leave publishAs out until the card answers it."New value: +"How the launch ends: draft in Adrails, paused on Meta, or live only after the person explicitly chooses live in the launch card. A typed live request is a suggestion; leave publishAs out until the card answers it. upload: only the files, to the media library."
    • changedInput schema / properties / input / properties / publishAs / enum
      Previous value: -[
      -  "draft",
      -  "paused",
      -  "live"
      -]New value: +[
      +  "draft",
      +  "paused",
      +  "live",
      +  "upload"
      +]
    • changedInput schema / properties / input / properties / settingsFromAdSet / description
      Previous value: -"The existing ad set whose settings the new ad set copies, when the person asks for the same settings as an ad set (\"same settings as STATIC\", \"même paramétrage que l'ad set X\"): its id from a mention or the account facts, or its name exactly as the person wrote it. Adrails reads its targeting, budget, optimization, bid, placements, Page, pixel and link from the account and never asks them; pass only the fields the person changes. With it, target is new_ad_set:<its campaign> unless the person named another campaign or a new one."New value: +"The ad set whose settings the new one copies (\"same settings as STATIC\", \"même paramétrage que l'ad set X\"): its id from a mention or the account facts, or its name as written. Adrails reads its targeting, budget, optimization, bid, placements, Page, pixel and link and never asks them; pass only what the person changes. With it, target is new_ad_set:<its campaign> unless they named another campaign or a new one."
    • changedInput schema / properties / input / properties / source / description
      Previous value: -"Where the creatives are, when the person said or it is plain: a mentioned folder, attached images. none only when the person said they will add the creatives later: the rest is then saved as a draft in Campaigns. When they have not said where the creatives are, omit it: the card asks."New value: +"Where the creatives are, when the person said or it is plain: a mentioned folder, attached images. none only when the person said they will add the creatives later: the rest is then saved as a draft in Campaigns. posts: existing Page posts are the ads (metaSettings.ad.existingPosts), as a draft too. When they have not said where the creatives are, omit it: the card asks."
    • changedInput schema / properties / input / properties / source / enum
      Previous value: -[
      -  "drive_folder",
      -  "images",
      -  "reuse",
      -  "none"
      -]New value: +[
      +  "drive_folder",
      +  "images",
      +  "reuse",
      +  "none",
      +  "posts"
      +]
    • changedInput schema / properties / input / properties / target / description
      Previous value: -"Where the person wants the ads, from the request, earlier turns or card: new_campaign, new_ad_set:<campaign id> or ad_set:<ad set id>."New value: +"Where the ads go: new_campaign, new_ad_set:<campaign id> or ad_set:<ad set id>."
    • removedInput schema / properties / input / properties / uiTranslations
      Removed value: -{
      -  "additionalProperties": {
      -    "maxLength": 1000,
      -    "type": "string"
      -  },
      -  "description": "Legacy, kept for stored briefs: omit it.",
      -  "propertyNames": {
      -    "maxLength": 500
      -  },
      -  "type": "object"
      -}
    • changedInput schema / properties / userStatement / description
      Previous value: -"The latest verbatim user request or free-text answer. Required: no Adrails card exists in MCP."New value: +"The user's request or answer for this launch, in their own words. Required: no Adrails card exists in MCP."
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare not read-only, non-destructive, closed-world, non-idempotent; the description adds the crucial behavior that nothing goes live or spends without browser approval and that the brief is a mutable artifact updated per call. It also discloses that returned names map only to IDs the tool itself supplied, which is a real constraint on how the agent may reuse identifiers. It does not mention the idempotencyKey requirement for mutations, though the schema does.

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?

Content is front-loaded: what the tool does, then the input contract, then return shape, then the handoff to campaigns_launch. Every sentence carries a distinct operational fact, but the middle sentences pack several constraints together and read densely rather than scannably.

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 multi-turn, mutation-adjacent tool with no output schema, the description covers lifecycle (prepare/continue), return shape (open questions with labels and named options), identifier provenance, and the approval gate before anything goes live. That is enough for an agent to call it correctly and to know what to do with 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 75% and the nested input object is heavily self-documented, so the bar is elevated; the description still adds meaning by defining the division of labor between userStatement (verbatim request) and input (confirmed choices only). It further specifies where a lead form id may come from (userStatement or metaSettings.ad.leadFormId) and that account/budget/launch mode must not be defaulted. It does not explain the optional accountIds or idempotencyKey parameters.

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 names a specific verb and resource — 'Prepares or continues a Meta launch brief' — and the following sentences scope it as a pre-launch brief builder rather than a launcher. It explicitly names the downstream tool (campaigns_launch) and the sibling used for form lookup (targeting_options), so an agent can place it in the workflow without opening a schema.

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 states the iterative contract clearly: each call with new answers updates the brief, and a completed brief is handed to campaigns_launch. It also gives a concrete sourcing rule ('The account, budget and launch mode come from the person, not from defaults') and a specific branch for Leads instant forms via targeting_options kind=lead-form. What is missing is any negative guidance about when not to call it, e.g. requests that belong to site_brief or campaigns_setup.

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.