Tencent Ad MCP Server

adgroups_delete

Delete a specific ad group from your Tencent Ads account by providing the account ID and ad group ID.

Instructions

删除广告组 (Delete ad group)

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

Input Schema

Name	Required	Description	Default
`account_id`	Yes	广告主账户ID
`adgroup_id`	Yes	广告组ID

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?

The description simply states the action (delete) but does not disclose behavioral traits such as irreversibility, required permissions, or cascading effects. Since no annotations are present, the description should provide this context.

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 very concise, consisting of a single phrase in both Chinese and English. It is front-loaded and efficient, though it could benefit from slightly more detail without becoming verbose.

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?

For a delete operation, the description is incomplete. It does not mention return values, error handling, or side effects. With no output schema, the description should provide more context to ensure the agent understands the tool's full behavior.

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 description coverage is 100% and both parameters have descriptions in the schema. The tool description does not add meaning beyond the schema, earning a baseline score of 3.

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 '删除广告组 (Delete ad group)' clearly states the verb (delete) and the resource (ad group), making the tool's purpose immediately obvious. It effectively distinguishes from sibling tools like adgroups_get and adgroups_update.

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. For example, there is no mention of prerequisites or when adgroups_update_configured_status might be more appropriate.

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