Tencent Ad MCP Server

dynamic_creatives_get

Retrieve a paginated list of dynamic creatives for a specified advertiser account, with optional filtering and field selection.

Instructions

获取创意列表 (Get dynamic creatives)

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": "dynamic_creatives_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

B3.3/5.0

Behavior2/5

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

No annotations are present, and the description lacks any behavioral details such as side effects, permissions, rate limits, or pagination behavior. For a read tool, basic safety traits should be mentioned.

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 extremely concise with two clauses (Chinese and English) that directly state the purpose. Every word earns its place, and it is front-loaded.

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 tool has 5 parameters and no output schema or annotations, the description is far from complete. It omits critical context about parameter usage, return format, and when to choose this over siblings.

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?

The description does not elaborate on any parameters. With schema description coverage at 20%, the description should compensate but fails to add meaning beyond the schema's type and default values.

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 '获取创意列表 (Get dynamic creatives)' clearly specifies the action (get list) and the resource (dynamic creatives). It distinguishes this tool from its siblings (add, update, delete) which use different verbs.

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives. However, the tool name and sibling names imply its role as a read operation, offering some implicit context.

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