Tencent Ad MCP Server

custom_audiences_get

Retrieves custom audience lists for a given ad account, enabling precise targeting and audience management.

Instructions

获取自定义人群列表 (Get custom audiences)

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>"
    },
    "name": "custom_audiences_get"
  }
}

Input Schema

Name	Required	Description
`page`	No
`fields`	No
`filtering`	No
`page_size`	No
`account_id`	Yes	广告主账户ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, so description fully responsible. It omits behavioral traits such as read-only nature, pagination, rate limits, or authentication needs. Only states the basic action.

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

Conciseness3/5

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

Single sentence, bilingual, no wasted words. However, it is too minimal for the complexity of the tool (5 parameters, potential pagination). Could be longer to add value.

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 no output schema, no annotations, and low param coverage, the description lacks explanation of return format, pagination behavior, or required permissions. Incomplete for effective use.

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

Parameters2/5

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

Schema description coverage is only 20% (account_id has description). The tool description adds no additional meaning to parameters like page, fields, filtering, page_size. With low coverage, description fails to compensate.

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 states the verb 'Get' and the resource 'custom audiences', clearly indicating a list retrieval operation. However, with siblings like custom_audiences_add, update, delete, it does not explicitly differentiate itself beyond the verb.

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 on when to use this tool vs alternatives like adgroups_get or custom_audiences_delete. No context about prerequisites, filters, or limitations.

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