Tencent Ad MCP Server

daily_reports_get

Retrieve daily performance reports for Tencent Ads across advertiser, campaign, ad group, or ad levels. Filter by date range and fields, and group results as needed.

Instructions

获取日报表数据 (Get daily reports)

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": {
      "level": "<level>",
      "date_range": "<date_range>",
      "group_by": "<group_by>",
      "fields": "<fields>"
    },
    "name": "daily_reports_get"
  }
}

Input Schema

Name	Required	Description
`page`	No
`level`	Yes	报表层级: REPORT_LEVEL_ADVERTISER / REPORT_LEVEL_CAMPAIGN / REPORT_LEVEL_ADGROUP / REPORT_LEVEL_AD
`fields`	Yes	返回字段
`group_by`	Yes	分组字段
`order_by`	No
`filtering`	No
`page_size`	No
`account_id`	No	广告主账户ID
`date_range`	Yes	日期范围

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Get daily reports', with no mention of read-only nature, authentication, rate limits, or side effects. This is insufficient for an AI agent to infer safety or constraints.

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?

The description is concise (one short line) but lacks structure. It is not verbose, but the brevity sacrifices clarity. It earns its place by being non-redundant, but could be expanded.

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

Completeness1/5

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

Given the tool's complexity (9 parameters, nested objects, no output schema), the description is severely incomplete. It does not explain return values, pagination behavior, filtering, or report content. An AI agent would lack critical context to use it effectively.

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 adds no parameter-specific information beyond what is already in the input schema. With 56% schema description coverage, the description should compensate but does not. It merely restates the tool's purpose.

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 explicitly states '获取日报表数据 (Get daily reports)', clearly indicating it retrieves daily report data. It distinguishes itself from sibling tools like 'hourly_reports_get' and 'async_reports_add' by specifying 'daily', though it could be more precise about the type of reports (e.g., advertising).

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. Sibling tools like 'hourly_reports_get' and 'async_reports_add' exist, but the description does not clarify scenarios for choosing this tool over them. No when-not-to-use or context is provided.

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