tiktok

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: tiktok
description: When a workflow needs public TikTok data through UnifAPI — creator profiles and engagement, videos and comments, hashtag and music feeds, or search. Also use on "find TikTok creators for," "pull videos for," "TikTok follower count," "search TikTok for," "rising hashtags," or when another skill (creator shortlist, audience fit, demand radar, local buzz) needs the deterministic TikTok read path. Connect via the `unifapi` skill first. Read-only research, never posts.
license: MIT
metadata:
  author: UnifAPI
  version: "1.0.0"
  homepage: https://unifapi.com/agents/tiktok
  source: https://github.com/unifapi-agent/agents
---

# tiktok

The deterministic read path for public **TikTok** data through UnifAPI. This is a
**Data Skill**: it does not run a marketing job on its own — it names the
concrete `tiktok/...` operations, response shapes, and gotchas so any creator- or
trend-first workflow (shortlisting, audience-fit, demand radar, local buzz) reads
from one known recipe instead of rediscovering the surface each time.

Read-only — **eyes, not hands**. It researches public TikTok data and returns
cited records; it never posts, comments, or follows, and UnifAPI never holds
TikTok credentials.

## Use the `unifapi` skill for live evidence

Connect once through the shared **`unifapi`** skill (OAuth MCP), then call the
operations below. TikTok users and videos are keyed by **numeric id** — resolve a
`@handle` or a video URL to its id first (see Gotchas). Keep any `billing`
metadata so the output can state record cost.

## Response contract

Single-entity endpoints return the object in `data`:

```json
{
  "request_id": "unif_...",
  "data": {},
  "billing": { "records_charged": 1, "balance_remaining": 99 }
}
```

List endpoints return an array in `data` plus `pagination`:

```json
{
  "request_id": "unif_...",
  "data": [],
  "pagination": { "has_more": false, "next_cursor": null },
  "billing": { "records_charged": 1 }
}
```

When `pagination.has_more` is true, pass `pagination.next_cursor` as the next
request's `cursor` (`limit` sets page size). Always preserve `billing`.

## Core operations

| Need                          | Operation                                                     |
| ----------------------------- | ------------------------------------------------------------- |
| Resolve handle → id           | `tiktok/users/resolve` (`?username=...`)                      |
| Resolve video URL → id        | `tiktok/videos/resolve` (`?url=...`)                          |
| Search videos / users         | `tiktok/search/videos` · `tiktok/search/users` (`?q=...`)     |
| Search hashtags / mixed       | `tiktok/search/hashtags` · `tiktok/search` (`?q=...`)         |
| Creator profile               | `tiktok/users/{id}`                                           |
| Creator videos                | `tiktok/users/{id}/videos`                                    |
| Followers / following / likes | `tiktok/users/{id}/followers` · `.../following` · `.../likes` |
| Video + reaction              | `tiktok/videos/{id}` · `tiktok/videos/{id}/comments`          |
| Hashtag feed                  | `tiktok/hashtags/{id}` · `tiktok/hashtags/{id}/videos`        |
| Music feed                    | `tiktok/music/{id}` · `tiktok/music/{id}/videos`              |

Need a field not listed here? Use the `unifapi` skill's `get_operation` to read
the exact schema before calling — but pick the operation from this table, don't
discover blind.

## Workflow

The deterministic recipes. Pick the one that matches the job; each names exactly
what to call.

1. **Discover by topic.** Call `tiktok/search/videos?q=...`,
   `tiktok/search/users?q=...`, or `tiktok/search/hashtags?q=...` for the niche;
   use `tiktok/search?q=...` for a mixed result.
2. **Resolve a creator.** Call `tiktok/users/resolve?username=...` to get the
   numeric id, then `tiktok/users/{id}` for `follower_count`, `like_count`, and
   `video_count`.
3. **Read engagem