ae_xigua_fetch_user_post_list
Retrieve a page of posts published by a Xigua user.
Inputs:
- user_id (required, string): The ID of the user whose posts you want to retrieve.
- max_behot_time (optional, string): Pagination cursor. Omit it or use an empty string for the first page. To request the next page, pass the previous response's last post's behot_time value as a string; the documented location is $.data.data[-1].behot_time.
Returns: A response containing the requested page of the user's posts. The response schema does not specify individual post fields. A single request is not guaranteed to return all posts.
First-page example: user_id="1922379661976311", max_behot_time="".
ae_xigua_fetch_video_comment_list
Retrieve comments for a Xigua video, one page at a time.
Inputs:
- item_id (required string): The video ID.
- offset (optional integer, default 0): Use 0 for the first request. For subsequent requests, use the offset returned by the previous response.
- count (optional integer, default 20): The requested number of comments. Keeping the default is recommended.
Returns: A response containing comment-list data for the specified video and requested page. The exact fields of individual comments are not specified.
Example input: {"item_id":"7354954305222377999","offset":0,"count":20}
ae_xigua_fetch_video_data
Retrieve limited data for one Xigua video.
Input: item_id is required and must be a video ID string, for example "7354954305222377999".
Result: Video-related data, including Base64-encoded playback addresses. Decode these addresses before using them for playback. The result does not include the title or comprehensive metadata, and it is not a video file download. Response data may be null; its detailed field structure is not specified.
ae_xigua_fetch_video_play_url
Retrieve a playback link for one Xigua video.
Input: item_id (required string), the video ID. Example: "7354954305222377999".
Result: A decoded, plaintext video playback URL that can be used directly without further decoding. The result is a link, not the video file.
ae_toutiao_get_article_info
Retrieve information about a specific Toutiao article.
Input: aweme_id is a required string containing the article ID, not the full URL. For https://www.toutiao.com/article/7450114952884503059/, use "7450114952884503059".
Result: The response's data contains the article information and may be null. The documented schema does not specify individual article fields. This tool looks up one known article; it does not search for articles.
ae_toutiao_get_comments
Retrieve comments for a specified Toutiao post, one page at a time.
Inputs (both required strings):
- group_id: The post ID, which can be extracted from its URL. For example, https://www.toutiao.com/i7453372680222523931/ has the ID "7453372680222523931".
- offset: The pagination offset. Supply "0" for the first page, then "20", "40", and so on for subsequent pages. This parameter must be supplied explicitly.
Returns: A response containing comment-list data for the requested post and offset. The documented response schema does not specify individual comment fields.
Example: {"group_id":"7453372680222523931","offset":"0"}.
ae_toutiao_get_user_id
Retrieve a Toutiao user's ID from their profile link.
Input: user_profile_url (required string) — the target user's Toutiao profile URL, such as a link beginning with https://www.toutiao.com/c/user/token/.
Result: A response containing the user ID (user_id) corresponding to the supplied profile. The exact ID payload structure is not specified. This tool resolves a profile link to an ID rather than searching for users by name or retrieving full profile details.
ae_toutiao_get_user_info
Retrieve information about a specified Toutiao user.
Input: user_id is required and must be a string containing the target user's ID, for example "1352838578180211". Obtain the user's ID before using this tool.
Result: a response containing user information in data and response status metadata. The data field may be null; the documented schema does not specify the individual user-information fields.
ae_toutiao_get_video_info
Retrieve information about a specified Toutiao video.
Input: aweme_id is required and must be a string containing the video's post ID. Extract the ID from the video URL rather than passing the full URL. For example, https://www.toutiao.com/video/7431543350882206242/ corresponds to aweme_id = "7431543350882206242".
Returns: a response whose data contains information about the specified video. Data may be null; the documented response does not specify individual video detail fields. This tool looks up a known video, rather than searching for videos or downloading video files.
ae_douban_get_movie_review_detail
Retrieve a single Douban long-form movie or series review by its ID. Provide the required reviewId as a string identifying the review, not the title. Use this to inspect a review already found in a title's review list. The response includes the lookup data and code, message, and recordTime; the fields within the review data are not specified. This tool does not search for or list reviews.
ae_douban_list_movie_comments
Retrieve a page of short audience comments for a Douban movie or TV title. Provide the title's subjectId; a title name alone is not sufficient. Optionally set page (default: 1) and sort: time for time ordering (default) or new_score for new-score ordering. The response includes comment data and status information. Individual comment fields and pagination metadata are not specified, and one page should not be treated as all comments.
ae_douban_list_movie_reviews
Browse a page of long-form audience reviews for a movie or TV series. Provide the entry's unique identifier as subjectId; optionally set page (default 1) and sort to time (by time, default) or hotest (by popularity). The response includes review-result data and status information. Individual review fields and pagination metadata are not specified by the response schema.
ae_douyin_xingtu_check_creator_visibility
Check whether a creator can be displayed in a selected content channel before adding them to a campaign shortlist. Provide the creator's unique ID in oAuthorId. Optionally set platform to SHORT_VIDEO (short video, the default), LIVE_STREAMING (live streaming), PICTURE_TEXT (image and text), or SHORT_DRAMA (short drama). The response includes a status code, result data, a message, and recordTime. Result data represents display availability; its internal structure is not specified. A failed request does not mean the creator is unavailable, and this check does not change visibility or confirm campaign participation.
ae_douyin_xingtu_get_creator_channel_metrics
Look up channel information for a Douyin creator in a selected content format. Provide the creator's unique ID in oAuthorId. The optional platform value is SHORT_VIDEO (short video, the default), LIVE_STREAMING (live streaming), PICTURE_TEXT (image-and-text posts), or SHORT_DRAMA (short drama). Each call returns information for one creator and one format, together with a response code, message, and record time. The data payload's detailed fields are not specified, so availability of particular metrics is not guaranteed. Query formats separately to support comparisons of a creator's channel presence.
ae_douyin_xingtu_get_creator_contract_basics
Look up a Douyin Xingtu creator's basic contract-related information for campaign planning. Provide the creator's unique ID in oAuthorId; optionally use range=DAY_30 for the last 30 days or range=DAY_90 for the last 90 days. No default period is specified if range is omitted. The response includes code, data, message, and recordTime; data holds the returned contract-related information, but its individual fields are not specified. This lookup does not create or modify contracts.
ae_douyin_xingtu_get_creator_side_basics
Look up a creator's basic sidebar information on Douyin's Xingtu marketplace to support shortlist screening. Provide the creator's unique ID as the required string parameter oAuthorId. The response includes the returned creator data, a status code, a message, and a record time. The fields within the creator data are not predefined, so available details depend on the response.