Skip to main content
Glama

tiktok-scraper-video-downloader-api-mcp

Get Commercial Ad Creative Detail

tiktok_ad_detail
Read-onlyIdempotent

Get full creative telemetry, 1080p ad video URL, CTR curve, and landing page URL for a TikTok Creative Center ad ID (10 credits).

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": {
      "ads_id": "<ads_id>"
    },
    "name": "tiktok_ad_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
ads_idYesNumeric TikTok Creative Center ad / material ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the description only needs to add value — and it does by disclosing the cost ('10 credits') and the returned artifacts including a 1080p video URL. It stops short of noting rate limits, failure modes for invalid/expired ad IDs, or pagination-style concerns, but the credit cost is a genuinely useful operational disclosure.

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?

A single front-loaded sentence with no filler, and the credit cost sits at the end where it is easy to scan. It is efficient, but the parenthetical pricing is the only structural break and the sentence is dense with a four-item payload list — appropriate but not exemplary framing.

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

Completeness5/5

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

One required string parameter, full schema coverage, rich annotations, and no output schema — the description correctly compensates by enumerating what comes back (telemetry, video URL, CTR curve, landing page URL) and flags the credit cost. Nothing material an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and already defines ads_id as a 'Numeric TikTok Creative Center ad / material ID', so the baseline is 3. The description earns an extra point by reinforcing that this is specifically a commercial Creative Center ad (or material) ID rather than an organic video ID, which helps disambiguate against the video-detail sibling.

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?

Specific verb ('Get') plus a concrete resource ('TikTok Creative Center ad ID') and an enumerated payload (creative telemetry, 1080p video URL, CTR curve, landing page URL). It implicitly separates itself from the organic tiktok_video_detail by scoping to Creative Center ads, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description narrows the input to a 'TikTok Creative Center ad ID', which implies the call should follow ad discovery (e.g. tiktok_top_ads), but it never states when to use this versus tiktok_video_detail or any other sibling, and gives no exclusions or prerequisites beyond the ID type.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources