Tencent Ad MCP Server

custom_audiences_add

Create custom audiences for Tencent Ads by specifying account, name, and type to target specific user groups.

Instructions

创建自定义人群 (Create custom audience)

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>",
      "audience_name": "<audience_name>",
      "audience_type": "<audience_type>"
    },
    "name": "custom_audiences_add"
  }
}

Input Schema

Name	Required	Description
`account_id`	Yes	广告主账户ID
`description`	No	人群描述
`audience_name`	Yes	人群名称
`audience_type`	Yes	人群类型

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create custom audience' without mentioning prerequisites, side effects, or safety implications (e.g., that creation is irreversible or requires specific permissions).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely terse (two words plus translation), which is not concise but under-specified. It lacks structure and fails to earn its place by providing any useful guidance beyond the tool name.

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 four parameters and no output schema, the description is incomplete. It does not explain return values, validation rules, or prerequisites. The agent is left with insufficient context to correctly invoke the tool.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema. Critical parameters like `audience_type` lack clarification on valid values or usage, which the description could have provided.

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?

The description clearly states the verb 'Create' and the resource 'custom audience', which distinguishes it from sibling tools like get, update, delete. However, it lacks specificity about the type of custom audience (e.g., from file, from events) which would further clarify its purpose.

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 vs alternatives. The sibling list includes related tools like custom_audiences_get and custom_audiences_update, but the description offers no context to help an agent choose appropriately.

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