Tencent Ad MCP Server

adgroups_update_bid_amount

Update the bid amount for an ad group by providing account ID, ad group ID, and new bid in cents.

Instructions

更新广告组出价 (Update ad group bid amount)

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

Input Schema

Name	Required	Description
`account_id`	Yes	广告主账户ID
`adgroup_id`	Yes	广告组ID
`bid_amount`	Yes	出价，单位分

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as whether the operation is reversible, requires special permissions, or has side effects. 'Update' implies mutation, but no further detail is given.

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?

Single sentence, bilingual, no waste. Efficient but could be slightly more structured with a separate usage note.

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?

Lacks any description of return values or side effects. Without output schema or behavioral notes, the agent may not know what to expect after the update (e.g., success confirmation, no content).

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% with descriptions for each parameter, so the schema already provides meaning. The description adds no additional semantic context beyond restating the parameter names.

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 clearly states the tool updates an ad group's bid amount. It is specific about the resource (ad group) and attribute (bid amount), but does not explicitly distinguish it from sibling tools like adgroups_update or adgroups_update_daily_budget.

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 versus alternatives (e.g., adgroups_update for broader updates or other bid-related tools). The description lacks usage context or prerequisites.

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