Tencent Ad MCP Server

videos_get

Retrieve a list of video assets for Tencent Ads. Filter by account and criteria to find specific videos for ad creatives.

Instructions

获取视频素材列表 (Get videos)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "videos_get"
  }
}

Input Schema

Name	Required	Description
`page`	No
`fields`	No
`filtering`	No
`page_size`	No
`account_id`	No	广告主账户ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description must cover behavioral traits. It only states the purpose and does not disclose pagination behavior, rate limits, or what happens with empty results. The filtering parameter implies behavior but is not explained.

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 very short (two words in Chinese plus English translation). While concise, it lacks structure and essential details. Every sentence should add value, but here it is too sparse.

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 no output schema and low parameter coverage, the description is severely incomplete. It does not specify return format, pagination details, or how to use the filtering parameter. The agent would struggle to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20% (only account_id described). The description adds no meaning to any parameter; it does not explain what 'page', 'fields', 'filtering', or 'page_size' do. This leaves the agent guessing.

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 purpose: '获取视频素材列表 (Get videos)'. It is a specific verb+resource indicating retrieval of video material list, distinguishing it from siblings like videos_update and videos_delete.

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 like images_get or when not to use it. There are no prerequisites or context about its use case.

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