SuperAPI AI Directory

linkfox-echotik-batch-video-detail

Design & creation

View repository

Updated 10-16 00:00

About this skill

EchoTik TikTok Batch Video Detail

This skill batch-fetches detailed performance metrics for TikTok videos you already have IDs or URLs for, helping sellers and marketers compare videos side-by-side using views, likes, comments, shares, video sales/GMV, and creator data.

Core Concepts

This tool retrieves full detail metrics for a batch of TikTok videos in a single call. You identify videos by ID and/or by TikTok video URL; the backend extracts the videoId from each URL and merges it with any IDs you supplied, then returns per-video analytics.

Input options (at least one is needed; both can be combined):

  • videoIds — array of TikTok video IDs (up to 1000)
  • videoUrls — array of TikTok video URLs (e.g. https://www.tiktok.com/@<unique_id>/video/<videoId> or https://www.tiktok.com/video/<videoId>); the trailing videoId is extracted from each URL and merged with videoIds (up to 1000)

Multi-period metrics: views and likes are each reported as a cumulative total plus 1d / 7d / 30d increments, so you can read both lifetime performance and recent momentum.

Engagement & attribution: comments, shares, favorites, estimated video sales (units), and estimated video sales GMV (amount) are returned per video.

Flag fields (salesFlagText / isAdText / createdByAiText): human-readable yes/no (AI: yes/no/unknown) labels for selling / ad / AI-generated videos.

vs. search: This is detail lookup for known videos (you already have IDs/URLs). To discover videos by region/filter (no IDs needed), use linkfox-echotik-list-video.

Data Fields

Field Type Description
videoId string Video ID
videoDesc string Video description/caption
officialUrl string TikTok official video URL
coverUrl string Video cover URL
duration integer Video duration (seconds)
width string Video width (px)
height string Video height (px)
ratio string Video resolution (e.g. 540p/720p)
dataSize string Video file size
createDate string Video publish date (yyyy-MM-dd HH:mm:ss)
userId string Creator ID
uniqueId string TikTok account ID (unique_id)
avatar string Creator avatar URL
totalViewsCnt integer Total play count
totalViews1dCnt integer Play count increment over the last 1 day
totalViews7dCnt integer Play count increment over the last 7 days
totalViews30dCnt integer Play count increment over the last 30 days
totalDiggCnt integer Total likes
totalDigg1dCnt integer Like increment over the last 1 day
totalDigg7dCnt integer Like increment over the last 7 days
totalDigg30dCnt integer Like increment over the last 30 days
totalCommentsCnt integer Total comments
totalSharesCnt integer Total shares
totalFavoritesCnt integer Total favorites
totalVideoSaleCnt integer Video sales (units, estimated)
totalVideoSaleGmvAmt integer Video sales GMV (estimated amount)
salesFlagText string Whether it is a selling video (yes/no)
isAdText string Whether it is an ad video (yes/no)
createdByAiText string Whether it is an AI video (yes/no/unknown)
productCategoryList string Associated product categories (JSON string, empty is[])
videoProducts string Video selling products (JSON string, empty is[])
region string Region code of the video
sourceType string Data source (e.g. Tiktok)
sourceTool string Source tool (e.g. EchoTik-Video List)

Parameter Guide

Parameter Type Required Default Description
videoIds array<string> No* - List of TikTok video IDs, up to 1000
videoUrls array<string> No* - List of TikTok video URLs (in the form https://www.tiktok.com/@<unique_id>/video/<videoId> or https://www.tiktok.com/video/<videoId>); extract the videoId at the end of each URL and merge it into videoIds, not mutually exclusive with videoIds, up to 1000

* Provide at least videoIds / videoUrls one of them; both can be passed at the same time, and the server merges and deduplicates before querying.

How to call

  • API endpoint:POST /echotik/batchVideoDetail(for full parameters/response/error codes see references/api.md)
  • Python script:python scripts/echotik_batch_video_detail.py '<JSON 参数>' [--inline]
  • Cost constraint: This tool consumes compute; by default, the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the zip code to probe continuously; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (default script behavior):

  • Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-echotik-batch-video-detail-<timestamp>.json(<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user task;writing to /tmp is prohibited, if the current directory is not writable, report an error)
  • Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
  • Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, length of the largest list field + first 3 samples)
  • Add --inline to force full printing to stdout (also written to disk)

Data reading recommendations: first check the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide problem resolution:

Abnormal situations

  • API Key not configured: environment variable not configured LINKFOX_AGENT_API_KEY, and also not configured LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with similar meaning.

Usage Examples

1. Batch lookup by video IDs

{
  "videoIds": ["7030893014180531462", "6768504823336815877", "7425631540178160939"]
}

2. Batch lookup by video URLs

{
  "videoUrls": [
    "https://www.tiktok.com/@sageandintuition/video/7030893014180531462",
    "https://www.tiktok.com/@<unique_id>/video/6768504823336815877"
  ]
}

3. Mixed IDs and URLs (merged server-side)

{
  "videoIds": ["7030893014180531462"],
  "videoUrls": ["https://www.tiktok.com/@<unique_id>/video/6768504823336815877"]
}

Display Rules

  1. Present a comparison table: Show one row per video with video description (truncated if long), views, likes, comments, shares, video sales, video GMV, publish date, and creator
  2. Link to original: When officialUrl is available, provide it so users can view the video on TikTok
  3. Cover image: If coverUrl is present, mention that video thumbnails are available
  4. Duration formatting: Convert duration (seconds) to a readable format (e.g. "2:45" for 165 seconds)
  5. Multi-period metrics: When relevant, surface the 1d/7d/30d views/likes breakdowns alongside the lifetime totals
  6. Estimation notice: Video sales and GMV are estimated values — remind users these are approximations
  7. Flag badges: Render salesFlagText (selling), isAdText (ad delivery), and createdByAiText (AI) so users can scan video types at a glance
  8. Missing video handling: If a requested video returns no record, list which IDs/URLs had no data so the user can verify them
  9. Result count: Always inform the user of total records returned

Important Limitations

  • Batch cap: Up to 1000 videos per request
  • Lookup only: This tool does not search/discover videos by region or filter — it resolves specific IDs/URLs you already have. To discover videos, use linkfox-echotik-list-video
  • URL extraction: For videoUrls, only the trailing videoId is extracted — ensure each URL ends with the video ID
  • Estimated data: Sales, GMV, and attribution figures are analytics estimates, not exact platform figures
  • JSON-string fields: productCategoryList / videoProducts are returned as JSON strings (empty when none, e.g. []) — parse before display if needed
  • No secondary processing: Results are live queries, not stored in a database; secondary SQL/data processing is not available

User Expression & Scenario Quick Reference

Applicable Scenarios

User Says Scenario
"query the details of these TikTok videos" Batch detail by video IDs
"pull the views/sales of these TikTok video links" Batch detail by video URLs
"batch analyze the performance of these TikTok videos" Batch lookup, surface metrics
"which of these TikTok videos has the highest views/sales" Batch lookup, compare columns
"are these TikTok videos selling/ad delivery/AI" Batch lookup, read flag fields

Not Applicable Scenarios

  • Discovering videos by region/filter (use linkfox-echotik-list-video)
  • TikTok product detail lookup (use linkfox-echotik-batch-product-detail)
  • Resolving a TikTok video download link (use linkfox-echotik-get-video-download-url)
  • TikTok creator/seller (store) analytics (use linkfox-echotik-seller-detail / linkfox-echotik-list-seller)
  • Non-TikTok platform video data

Boundary Judgment

When users say "analyze these TikTok videos", check whether they already have specific video IDs or TikTok video URLs (this skill) or want to find videos by region/filter (the list-video skill). If they paste a list of IDs/URLs and want views/likes/sales/GMV details, this skill applies. If they ask "find popular TikTok videos" or "search videos by region", it does not — use linkfox-echotik-list-video to discover first.

Compute consumption rules

Consumes 5 compute.

Users pay fees due to compute consumption. Please fully assess: when this skill needs to be called at high frequency, or when the user's expectation of compute consumption is insufficient, be sure to remind the user, and let the user decide whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.


For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.