Tencent Ad MCP Server

dynamic_creatives_delete

Remove unwanted dynamic creatives from your Tencent Ads account by specifying the account ID and creative ID.

Instructions

删除创意 (Delete 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>",
      "dynamic_creative_id": "<dynamic_creative_id>"
    },
    "name": "dynamic_creatives_delete"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes	广告主账户ID
`dynamic_creative_id`	Yes	创意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, so the description must disclose behavioral traits. It only says 'Delete' without mentioning irrevocability, authorization needs, or cascading effects. For a destructive operation, this is insufficient.

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 a single sentence with no waste. It includes both Chinese and English for clarity. However, it is extremely brief and could be expanded slightly without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 required params, no output schema), the description is minimally adequate. It states the core purpose but lacks details about post-deletion behavior or error conditions.

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 input schema already documents both parameters. The description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.

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 clearly states the action (delete) and the resource (dynamic creative). It distinguishes from sibling delete tools like videos_delete and custom_audiences_delete by specifying the resource type.

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, such as prerequisites or situations to avoid deletion. Lacks any context to help an agent decide between this and other delete tools.

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