Tencent Ad MCP Server

dynamic_creatives_add

Creates a dynamic creative for an ad group by specifying account and ad group IDs, using templates and components to generate personalized ads.

Instructions

创建创意 (Create dynamic creative)

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": {
      "account_id": "<account_id>",
      "adgroup_id": "<adgroup_id>"
    },
    "name": "dynamic_creatives_add"
  }
}

Input Schema

Name	Required	Description
`account_id`	Yes	广告主账户ID
`adgroup_id`	Yes	广告组ID
`creative_components`	No	创意组件
`creative_template_id`	No	创意模板ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided. The description only states 'create' but does not disclose any behavioral traits such as required permissions, side effects, or whether the creation is immediate or async. The agent gains no insight beyond the verb.

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?

The description is a single concise sentence in Chinese with English translation. No wasted words, front-loaded with the core purpose.

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?

Given 4 parameters, with a nested object (creative_components) and no output schema, the description is too minimal. It does not explain the structure of creative_components, the role of creative_template_id, or expected outcomes. A more complete description would outline these.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%: all 4 parameters have descriptions in the schema. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not compensate with extra context.

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 explicitly states 'Create dynamic creative' which clearly identifies the action (create) and the resource (dynamic creative). This distinguishes it from sibling tools like dynamic_creatives_get, dynamic_creatives_update, etc.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when to use dynamic_creatives_add vs dynamic_creatives_update). No prerequisites or contextual hints are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.