Provided by TikHub
TikTok follower list of specified user
Follower list of specified user from TikTok via TikHub. One request per call; TikHub bills the request whether or not data comes back, and an empty data envelope is reported as no result.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the TikHub endpoint /api/v1/tiktok/app/v3/fetch_user_follower_list on Glasser.glasser run -p tikhub -e '/api/v1/tiktok/app/v3/fetch_user_follower_list' -i '{"sec_user_id":"MS4wLjABAAAA0lKrE0cVLLZCnVil-n-YEZlOoik9oeO3zOYQ08dqOEOw2pRSXWJdcSFw7lZeZcSP"}' --endpoint-version 1Uses endpoint version 1. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"tikhub","endpoint":"/api/v1/tiktok/app/v3/fetch_user_follower_list","input":{"sec_user_id":"MS4wLjABAAAA0lKrE0cVLLZCnVil-n-YEZlOoik9oeO3zOYQ08dqOEOw2pRSXWJdcSFw7lZeZcSP"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to check an audience relationship, you might look for a particular account among the follower or following records available in the response.
Copy this prompt into your agent to look for an account in the returned audience records.
Use tikhub:/api/v1/tiktok/app/v3/fetch_user_follower_list on Glasser.
Find my chosen account among the audience accounts returned by this endpoint.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"count": {
"type": "integer",
"description": "Number, do not exceed 20, keep it fixed."
},
"user_id": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "User ID, this is a pure numeric version of the user ID (one of user_id and sec_user_id)"
},
"min_time": {
"type": "integer",
"description": "Minimum time for paging, use default value 0 for the first request, and use the min_time value returned by the last request for subsequent requests."
},
"page_token": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Page token, use default value \"\" for the first request, and use the page_token value returned by the last request for subsequent requests."
},
"sec_user_id": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "User sec_user_id, this is a mixed letter and number version ID (one of user_id and sec_user_id)"
}
},
"additionalProperties": false
}{
"sec_user_id": "MS4wLjABAAAA0lKrE0cVLLZCnVil-n-YEZlOoik9oeO3zOYQ08dqOEOw2pRSXWJdcSFw7lZeZcSP"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Data returned or no match | The same price with or without matching data. | $0.0015 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |