hashtag-tracker git:20260908.495293dA

Immutable. This exact content never changes and is served at /api/v1/blob/57a09ddf63eecb02.

---
name: hashtag-tracker
description: "Track hashtag performance across Instagram, TikTok, Twitter, and Xiaohongshu simultaneously. Monitors post volume, engagement rates, top contributors, and content patterns for campaign tracking, trend research, and community activation measurement."
---

# Hashtag Tracker

Track hashtag performance across Instagram, TikTok, Twitter, and Xiaohongshu simultaneously. Monitors post volume, engagement rates, top contributors, and content patterns for campaign tracking, trend research, and community activation measurement. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

## Capability identifiers

- `instagram_v3_hashtag_posts`
- `tiktok_app_v3_hashtag_video_list`
- `twitter_web_search_timeline`
- `xiaohongshu_app_v2_search_notes`
- `douyin_search_challenge_search_v2`

## Workflow

1. Understand the user's research question, target, and context.
2. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.
3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- Always call `sandbase_inspect` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.