Skip to main content
Glama

Create a TikTok ad identity

ads_create_identity

Create a brand identity for TikTok ads from a display name and an avatar image URL or staged upload.

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>",
      "displayName": "<displayName>",
      "avatar": "<avatar>"
    },
    "name": "ads_create_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
avatarYes
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.
adAccountIdYes
displayNameYes

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds one genuinely useful behavioral detail — that the avatar may be an external URL or a staged upload (implying an upload step must precede the call) — but says nothing about permissions, duplicate handling, or what the resulting identity contains.

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?

A single front-loaded sentence with no filler and the key inputs surfaced immediately. It is efficient, though the space saved comes at the cost of the routing and platform detail an agent needs.

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

Completeness2/5

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

For a 6-parameter, 3-required mutation with no output schema and open-world behavior, the description is far too thin. It never explains the required adAccountId, the accountId/profileId/platform routing, or avatar constraints — everything an agent needs to call this correctly beyond the display name.

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?

Incorrect score placeholder replaced below.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource ("Create a brand identity for TikTok ads") and names the two inputs, so an agent can distinguish it from ads_list_identities or ads_create_account. However, framing it as TikTok-only conflicts with the schema's platform enum, which also accepts meta_ads and linkedin_ads, so the scope is slightly misleading.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to check ads_list_identities for an existing identity first, no prerequisites (connected ad account, prior staged upload step), and no mention of the accountId/profileId routing choice. The agent learns what the tool creates but not under what conditions to pick it.

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