Fetch details for a single TikTok Creative Center Top Ads material using its material_id. Returns structured ad detail for analysis or monitoring.
Retrieve TikTok Top Ads detail. Returns detail for one TikTok Creative Center Top Ads material. Use material_id; the upstream does not accept id or materialId.
| Name | Required | Description | Default |
|---|---|---|---|
| material_id | Yes | Top Ads material id |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully convey behavioral traits. It discloses that the upstream API has specific parameter naming requirements, but does not mention whether the tool is read-only, requires authentication, has rate limits, or returns any side effects. The description is minimally transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of three concise sentences with no redundant information. The purpose is stated first, followed by what is returned, and then a critical usage note. It is appropriately sized and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the single parameter and no output schema, the description adequately explains the tool's purpose and usage. However, it lacks information about the structure of the returned detail, potential error scenarios, or any additional context needed for complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage for the single parameter 'material_id', but the description adds value beyond the schema by indicating that the upstream rejects other parameter names ('id' or 'materialId') and emphasizing the correct key. This helps avoid invoking errors.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Retrieve TikTok Top Ads detail' with the specific resource 'one TikTok Creative Center Top Ads material'. It uses a specific verb and resource, and implicitly distinguishes from sibling tools like 'tiktok_top_ads_list' which returns multiple items.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear guidance on which parameter to use ('Use `material_id`') and explicitly warns that the upstream does not accept other parameter names like 'id' or 'materialId'. However, it does not explicitly state when to use this tool versus alternatives like 'tiktok_top_ads_list'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.