Skip to main content
Glama

Ads Uploader: Meta Ads MCP

Save Build

ads_save_build

Save a durable build: a launch configuration the web uploader can open and ads_create can launch by buildId. A spec-only build is the supported shape for agent-created configurations; the web uploader generates its own webState when it opens the build, and webState is only accepted unchanged from a build that was read. accountId can be omitted when the spec or webState carries it. Returns the build metadata with its url, launchable and launchBlockers, and display: totalAdSets, totalAds and the ads in each ad set as the web uploader renders them (display.complete false carries a reason, and display.inheritedFromSource lists fields that come from the source ad or preset). launchable describes headless ads_create launches only; any build opens in the web uploader. A saved build uses the campaign and ad set of its template ad, or new ones. Video items take the numeric Facebook video id (videoId in the upload result) as mediaId. Each call saves a new build; ads_update_build changes an existing one. Uploaded media accepts texts.common.multiAdvertiserAds only (boolean); omit to copy the source, which is off when the source ad does not say. True is refused while site links remain. Imported posts keep per-row choices. Website highlights is copied from the source and cannot be changed; none, all off and empty features never change it. Preview and saved display report both settings separately. video_uncrop and translate_voiceover require source OPT_IN.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional durable build name.
specNoPortable launch specification. Spec-only creation is supported and preferred for agent-created builds.
notesNoOptional free-form notes stored on the build.
webStateNoOpaque web uploader session snapshot. Do not construct it by hand. Only provide webState when round-tripping a snapshot previously read from a build without changing its structure.
accountIdNoOptional ad account ID. The server can also derive it from webState.selectedAccount.accountId, webState.selectedAccount.account_id, or spec.accountId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive save operation. The description adds substantial behavioral context beyond that: return metadata including url, launchable and launchBlockers; display completeness and inherited fields; and constraints such as multiAdvertiserAds only being accepted while site links remain, plus source OPT_IN requirements for video_uncrop and translate_voiceover. It does not contradict 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.

Conciseness3/5

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

The opening sentences are front-loaded and useful, but the body becomes a dense wall of edge cases covering display semantics, media options, inherited source fields, website highlights, preview behavior, and OPT_IN requirements. The information is often relevant, yet it is not organized into scannable units and several clauses could be tightened.

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 build-saving tool with no output schema, the description is unusually complete: it explains return values, launchability semantics, display reporting, source inheritance, media constraints, and several refusal conditions. An agent has enough context to call this correctly in common and many edge-case scenarios.

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, but the description still adds meaningful meaning for the complex inputs: accountId can be omitted when spec or webState carries it, webState must not be hand-constructed, and video items take the numeric Facebook video id as mediaId. The simple name and notes parameters are left to the schema, which is appropriate.

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 gives a specific verb and resource ('Save a durable build') and immediately distinguishes the object's role: a launch configuration the web uploader can open and ads_create can launch by buildId. It also names ads_update_build as the tool for changing an existing build, so an agent can separate it from siblings without opening another 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?

It explicitly states that spec-only builds are the supported shape for agent-created configurations, that webState is only accepted when round-tripping an unchanged snapshot, and that each call saves a new build while ads_update_build changes an existing one. Those are concrete when-to-use and when-not-to-use conditions with the main alternative named.

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.