Skip to main content
Glama

AdsAgent — TikTok Ads MCP

campaigns_quick_create

Prepare one TikTok create operation in new, append-campaign, or append-adgroup mode. Returns a confirm_token and a human-readable summary; does NOT publish until campaigns_quick_create_confirm is called with the token.

REQUIRED (always): advertiser_id (call assets_list_ad_accounts to discover), a saved template_id or exact template_name, plus exactly one creative source: tenant-owned creative.creative_id from creatives_list with readiness.create_eligible=true, ordered local creative.image_creative_ids for one carousel, or creative.{video_id | image_ids | tiktok_item_id}. A local creative_id is synced to the exact advertiser only after explicit confirmation. For Spark, pass the complete identity_id, identity_type, tiktok_item_id, and spark_receipt row from spark_ads_list_posts unchanged as creative; the server moves the identity fields into TikTok's native ad parameters and rejects any conflicting duplicate values. Set ad_params.ad_format to one of that row's supported_ad_formats values; the signed receipt rejects a video/carousel mismatch before approval.

TEMPLATE SETTINGS: read templates_get.effective_creation_defaults and let the server fill saved campaign/ad-group/ad settings. MCP new and append modes require a saved template; without a selector, preparation returns needs_input/template_required. The resolved campaign_params.objective_type (APP_PROMOTION / WEB_CONVERSIONS / VIDEO_VIEWS / LEAD_GENERATION), adgroup_params.{optimization_goal, billing_event, bid_type}, ad_params.ad_format (SINGLE_VIDEO / SINGLE_IMAGE / CAROUSEL_ADS) must form a supported recipe. WEB_CONVERSIONS also requires adgroup_params.pixel_id; APP_PROMOTION requires adgroup_params.app_id from assets_list_apps. APP RECIPES (Smart+): one app_id per campaign — dual Android+iOS means two prepares. iOS APP_IOS defaults campaign_type=IOS14_CAMPAIGN, campaign BUDGET_MODE_INFINITE (ABO), adgroup BUDGET_MODE_DYNAMIC_DAILY_BUDGET 50. Android APP_ANDROID defaults campaign_type=REGULAR_CAMPAIGN, campaign BUDGET_MODE_DYNAMIC_DAILY_BUDGET 50 (CBO), adgroup BUDGET_MODE_INFINITE. Both use placement AUTOMATIC (TikTok+Pangle+GAB), optimization_goal=IN_APP_EVENT, and deep_bid_type=AEO when optimization_event is set (SUBSCRIBE is the live reference event). Pass app_id and a create_eligible local creative. When the advertiser has exactly one BC_AUTH_TT identity (TikTok's FB-page analog), the server fills identity_id / identity_type / identity_authorized_bc_id. Do not rewrite IOS14_CAMPAIGN to REGULAR_CAMPAIGN. INSTALL_NOW is the default CTA when neither call_to_action nor call_to_action_id is set. Local READY_LOCAL images/videos from creatives_list with readiness.create_eligible=true are valid App ad sources via creative.creative_id — do not require a TikTok Material Center image_id first. A web landing_page_url is stripped on APP_PROMOTION unless a deeplink is also present. Regular ads that can deliver on TikTok also require ad_params.call_to_action or ad_params.call_to_action_id; for Spark Pull, LEARN_MORE is the documented minimum CTA example. REGULAR CAROUSEL: CAROUSEL_ADS is compatible only with TRAFFIC, WEB_CONVERSIONS, APP_PROMOTION, LEAD_GENERATION, PRODUCT_SALES, CATALOG_SALES, or REACH; correct the selected objective or ad_format explicitly, never auto-rewrite the objective. REGULAR LOCAL MEDIA: exact advertiser-linked CUSTOMIZED_USER is required for local video/image. AUTH_CODE is Spark-only on regular create: use an eligible Spark post and pass its signed receipt unchanged when available; a legacy receipt-less item incurs one bounded live provider verification before approval. TT_USER and BC_AUTH_TT are not regular-local choices and may be used only on a server-verified compatible Smart+ route.

REGULAR CAMPAIGN BUDGET: new regular campaigns default a missing campaign_params.budget_mode to BUDGET_MODE_INFINITE (non-CBO / ABO). Bounded DAY, DYNAMIC_DAILY_BUDGET, or TOTAL modes require a positive campaign budget, and dynamic daily mode requires budget_optimize_on=true (CBO). Meta-portable aliases campaign_params.budget_level=CBO|ABO|campaign|adgroup are accepted and rewritten to those native fields. Append modes reuse their existing campaign and do not apply this contract.

REGULAR AD-GROUP BUDGET/SCHEDULE: new and append-campaign modes require adgroup_params.budget_mode (BUDGET_MODE_DAY, BUDGET_MODE_DYNAMIC_DAILY_BUDGET, or BUDGET_MODE_TOTAL) plus a positive budget. Daily modes default a missing schedule to SCHEDULE_FROM_NOW; stale template start/end values are removed and the UTC start is stamped only at write time. BUDGET_MODE_TOTAL requires SCHEDULE_START_END with both UTC timestamps. Smart+ and append-adgroup do not use this new-ad-group contract.

WITH template_id or template_name (Meta-portable): pass just advertiser_id + template_name (or template_id) + creative — propose pulls campaign_params / adgroup_params / ad_params from the template (caller-set keys win), derives campaign_name/adgroup_name from template.campaign_naming / template.adgroup_naming, stamps ad_name as {adgroup_name}-{utc}, and reads is_smart_plus from template.campaign_params.is_smart_performance. The selected media determines the compatible image/video format; do not force SINGLE_VIDEO onto a local image from a video template. Smart+ APP_PROMOTION defaults call_to_action to INSTALL_NOW. Meta copy aliases title/headline→display_name, body/text/message→ad_text, and cta→call_to_action are accepted. App display_name defaults from the linked app name.

TEMPLATE/ROOT COMPATIBILITY: prefer the compact template selector plus creative shape above, with overrides in campaign_params / adgroup_params / ad_params and execution. adset_params is accepted as an adgroup_params alias; both maps are preserved for conflict validation. A templates_get row spread may supply id, name, and campaign_naming as selector echoes; other read-only row metadata is ignored. Supported root budget, counts, statuses, bid, schedule, Smart+ switches, copy, and identity fields are passed to the same normalizer as execution/native fields. Conflicting duplicates must be corrected before confirmation.

AUTO-FILLED FROM USER ASSETS: identity_authorized_bc_id (when identity_type=BC_AUTH_TT), promotion_type/app_type/package/app_download_url (for APP_PROMOTION when app_id is set), placements default to [PLACEMENT_TIKTOK] for PLACEMENT_TYPE_NORMAL, top-level targeting fields (location_ids, operating_systems, age_groups, …) fold into adgroup_params.targeting.

INITIAL STATUS: omit entity status fields such as campaign_params.status, adgroup_params.status, and ad_params.status; status is unsupported. Where a native field is needed for payload compatibility, use operation_status. Campaign, ad group, and ad statuses default to DISABLE; explicit ACTIVE/ENABLE is preserved in the approved plan. Smart+ adgroup/create does not accept operation_status. When a new Smart+ ad group is requested DISABLE, a separate durable post-create disable step must be acknowledged before ad creation. ENABLE requires no disable step.

SMART+ IMAGE MUSIC: SINGLE_IMAGE and CAROUSEL_ADS require a music_id because TikTok's image creative wire requires music. When music_info is omitted (or music_id is auto/random), the server selects one advertiser-available track from assets_list_music and revalidates that exact ID on the recorded create route. An explicit music_id still wins. Append-adgroup may inherit one unambiguous parent track. Preserve an explicit template track, including across advertisers, and verify that exact ID for the target; unavailable music requires another explicit selection, never silent replacement. If no usable track is available, use a video creative.

LOCAL IMAGE GROUPS: creative.image_creative_ids is an ordered list of 2..35 JPEG/PNG images for one native CAROUSEL_ADS creative, and the same field is accepted inside ad_params.creative_list[].creative_info for one carousel variant. Use only create_eligible image rows from the tenant library. SINGLE_IMAGE is a separate format; one image is not a native multi-card carousel. For TikTok Android App carousel ads, use CAROUSEL_ADS with music and the ordered image group. Do not split cards into separate creative_list entries or pass local IDs as provider image_ids. Inspect the prepared plan's final format and ordered members before confirmation. If the receipt reports creative_image_not_ready, wait the returned retry_after_seconds (10s), then prepare the same local IDs for a new approval; existing acknowledged image uploads are reused. creative_image_not_usable requires different eligible material. An uncertain upload must be reconciled, never automatically reuploaded or replayed.

META EXECUTION BLOCK: pass execution like Meta QuickCreate — execution.budget.level=campaign|adset (CBO/ABO), execution.budget.type=daily|lifetime, execution.budget.amount, execution.is_smart_plus / execution.advantage_plus / execution.is_smart_performance for Smart+, execution.statuses.{campaign,adset,ad} (ACTIVE/PAUSED -> ENABLE/DISABLE), execution.bid.{strategy,cap}, execution.start_time / execution.end_time, execution.start_mode (immediate or tomorrow = advertiser TZ next day 00:05 UTC wire), and legacy flat execution.budget_level / execution.budget_amount. execution.campaign_count and execution.adset_count expand into a bounded serial batch (product <= 20, append_mode=new only). creative_distribution=all_per_adset (default) keeps Smart+ multi-creative on one ad via ad_params.creative_list; one_per_adset expands Smart+ to one ad group per creative (not Meta ad objects).

OPTIONAL: creative_distribution (all_per_adset|one_per_adset), is_smart_plus (bool, default derived from template), execution (object), call_to_action_id (str — portfolio id, alternative to ad_params.call_to_action enum), campaign_params.budget_level (CBO/ABO).

APPEND MODES (TikTok-native): append_mode="append-campaign" with target_campaign_id creates one ad group + one ad under that exact campaign; omit campaign_params. append_mode="append-adgroup" with target_adgroup_id creates one ad under that exact ad group; omit campaign_params and adgroup_params. Existing APP_PROMOTION ad groups keep their app_id / promotion_type; pass only the new ad plus a create_eligible local creative_id, ordered image_creative_ids, or provider image_ids. The server verifies advertiser ownership, exact authorization route, parent status, hierarchy, and Smart+ compatibility before prepare and again before mutation. Do not use Meta append-adset naming, do not guess by name, and never supply both target IDs.

If required fields are missing, returns status="needs_input" with bounded rejected_paths and next_action — fix and re-call. Confirm tokens expire after 10 minutes. Successful proposals include a summary with recipe and launch_readiness, matching the dashboard's core readiness model. Smart+ is intentionally limited to locally verified recipes: APP_PROMOTION, WEB_CONVERSIONS, PRODUCT_SALES, and LEAD_GENERATION.

EXAMPLE (template path, Meta-portable name): campaigns_quick_create({"advertiser_id": "7563...", "template_name": "iOS14 AEO", "creative": {"creative_id": ""}})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bidNo
ctaNo
bodyNo
nameNo
textNo
titleNo
budgetNo
ad_nameNo
ad_textNo
bid_capNo
messageNo
creativeNo
end_timeNo
headlineNo
statusesNo
ad_paramsNo
ad_statusNo
executionNo
smart_plusNo
start_modeNo
start_timeNo
adset_countNo
append_modeNonew
budget_modeNo
budget_typeNo
identity_idNo
template_idNo
adgroup_nameNo
adset_paramsNo
adset_statusNo
bid_strategyNo
budget_levelNo
daily_budgetNo
display_nameNo
adgroup_countNo
advertiser_idYes
budget_amountNo
campaign_nameNo
identity_typeNo
is_smart_plusNo
template_nameNo
adgroup_paramsNo
adgroup_statusNo
advantage_plusNo
call_to_actionNo
campaign_countNo
campaign_namingNo
campaign_paramsNo
campaign_statusNo
call_to_action_idNo
target_adgroup_idNo
target_campaign_idNo
is_smart_performanceNo
campaign_daily_budgetNo
creative_distributionNo
identity_authorized_bc_idNo

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?

With no annotations, the description carries full burden, and it delivers: it discloses the non-publishing prepare/confirm separation, returns needs_input with rejected_paths, 10-minute confirm-token expiry, default entity statuses of DISABLE, server-side auto-fills, music selection behavior, and retry handling for creative_image_not_ready. It also reveals mutation-affecting nuances like 'a separate durable post-create disable step must be acknowledged before ad creation' and 'unavailable music requires another explicit selection, never silent replacement.'

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 front-loaded with the core purpose and requirements, and organized by bolded CAPS section headers. However, it is extremely long and dense, covering edge cases in a style that requires careful parsing. Most sentences earn their place given the tool's complexity, but a tighter structure would improve scannability for an agent.

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?

Given 57 parameters, no annotations, and no output schema, the description is remarkably complete. It covers modes, required inputs, recipe validation rules, budget and schedule contracts, Smart+ specifics, local image groups, Meta execution block, append behaviors, error handling, and token expiry. The example call at the end further anchors correct usage.

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 description coverage is 0%, so the description must compensate, and it does comprehensively. It explains the meaning and relationships of the central parameters (advertiser_id, template_id/name, creative, ad_params, campaign_params, adgroup_params, execution, append_mode) and Meta aliases like title/headline→display_name. It covers defaults (e.g., INSTALL_NOW, placements to PLACEMENT_TIKTOK) and conditional requirements (pixel_id for WEB_CONVERSIONS, app_id for APP_PROMOTION).

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 opens with a specific verb and resource: 'Prepare one TikTok create operation in new, append-campaign, or append-adgroup mode.' It also names the sibling companion ('does NOT publish until campaigns_quick_create_confirm is called'), making the tool's role in the two-step create flow unmistakable. The required inputs are enumerated, fully distinguishing it from related create/list tools.

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?

Explicit guidance covers when to use template selection vs manual params, append modes, and numerous 'do not' rules: 'Do not rewrite IOS14_CAMPAIGN to REGULAR_CAMPAIGN', 'never auto-rewrite the objective', 'do not guess by name, and never supply both target IDs.' It names prerequisite calls (assets_list_ad_accounts, creatives_list, spark_ads_list_posts) and directs the agent away from Meta conventions where inappropriate.

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