Tencent Ad MCP Server

custom_audiences_update

Modify custom audience name or description to refine ad targeting in Tencent Ads.

Instructions

更新自定义人群 (Update 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_id": "<audience_id>"
    },
    "name": "custom_audiences_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are present, and the description fails to disclose behavioral traits such as required permissions, side effects, rate limits, or return behavior. For a mutation tool, this lack of transparency is a significant gap.

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 extremely concise, consisting of a single bilingual phrase. It front-loads the essential information with no wasted words, though it might be slightly too minimal.

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 the absence of an output schema and annotations, the description should explain what the tool returns and any side effects. It does neither, leaving the agent with incomplete context for a mutation operation.

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?

The input schema already describes all four parameters with 100% coverage, including required fields account_id and audience_id. The description adds no additional semantic meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'Update custom audience', clearly identifying the action (update) and the resource (custom audience). Among sibling tools like custom_audiences_get, custom_audiences_add, and custom_audiences_delete, this tool's purpose is distinct and unambiguous.

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 such as custom_audiences_add or custom_audiences_delete. There is no mention of prerequisites, context, or scenarios where this update should be preferred over other operations.

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