Skip to main content
Glama

Create a TikTok video campaign

ads_create_tiktok_campaign

Create a TikTok campaign, ad group and video ad, all disabled, from a video URL or staged upload. Nothing spends until ads_set_status activates the ad (with campaignRecordId, that also enables its campaign and ad group). Location ids come from ads_list_targeting; an identity from ads_list_identities, or pass displayName and avatar to create one. dailyBudget is whole currency units, at least 20 USD. startDate must be after today in the ad account's timezone. Reuse the same idempotencyKey when retrying.

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": {
      "adAccountId": "<adAccountId>",
      "campaignName": "<campaignName>",
      "goal": "<goal>",
      "dailyBudget": "<dailyBudget>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "targeting": "<targeting>",
      "creative": "<creative>",
      "identity": "<identity>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "ads_create_tiktok_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
endDateYes
creativeYes
identityYes
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
startDateYes
targetingYes
adAccountIdYes
dailyBudgetYes
campaignNameYes
idempotencyKeyYesA unique value per intended campaign, such as a UUID. Sent as the Idempotency-Key header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"meta_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given."New value: +"meta_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "meta_ads",
      -  "tiktok_ads"
      -]New value: +[
      +  "meta_ads",
      +  "tiktok_ads",
      +  "linkedin_ads"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds behavior the annotations cannot express: three objects are created at once but disabled, no spend occurs until ads_set_status runs, campaignRecordId cascades activation to campaign and ad group, startDate must be after today in the ad account's timezone, and the same idempotencyKey must be reused on retry. That is exactly the operational context an agent needs for a non-destructive, open-world mutation.

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?

Every sentence carries a distinct constraint or routing rule, front-loaded with what gets created and its disabled state. No filler, no restatement of the title.

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?

Covers the creation semantics, safety gating, and prerequisites well for a complex nested 10-required-param tool with no output schema. The one gap is that it never states what the response returns (presumably the campaignRecordId and ad group/ad ids referenced indirectly), which matters for chaining into ads_set_status.

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?

With only 31% schema coverage across 13 parameters, the description compensates on the non-obvious ones: dailyBudget is whole currency units with a 20 USD floor, startDate timezone-relative constraint, provenance for locationIds and identity, and idempotencyKey semantics. It leaves the creative sub-fields (adText, coverImage, callToAction, landingPageUrl), goal enum, and targeting facets undocumented, but most of those are self-describing enums or schema-described.

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?

States a specific verb and full resource set ('Create a TikTok campaign, ad group and video ad') plus the initial state ('all disabled') and accepted creative sources. This cleanly separates it from ads_create_campaign, ads_create_linkedin_campaign and the ads_create_identity sibling.

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?

Gives concrete workflow routing: location ids from ads_list_targeting, identity from ads_list_identities or inline, and activation only via ads_set_status. It does not explicitly state when to prefer this over the generic ads_create_campaign (e.g. by platform), so it stops short of full alternative framing.

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