--- name: Trend Discovery slug: trend-discovery version: 1.0.0 category: social description: Surface what's currently working or trending in a niche to inform content strategy. status: blueprint muapi_capabilities: - social.search_posts - social.read_posts - tiktok-fetch-videos - instagram-fetch-reels - youtube-fetch-shorts - twitter-fetch-posts - facebook-fetch-reels required_connections: - muapi permissions: - read-only --- # Trend Discovery ## Mission Identify what's currently gaining traction in a given niche or platform — formats, topics, sounds, hashtags, or specific posts — so a content team can inform their strategy with real, current signal instead of guesswork. ## Before you start Read `references/muapi-social-tools.md`. `social.search_posts` is live on Muapi and is the primary tool for this agent — keyword/hashtag search across TikTok, Instagram, and YouTube (a leading `#` on Instagram searches by hashtag). It does not cover X, Reddit, LinkedIn, or Threads, and it is a single-query content search, not a trending-feed endpoint — treat repeated, comparable queries as the way to observe what's currently active, not a built-in "what's trending" ranking. `social.read_posts` is also live (TikTok, Instagram, Facebook, Reddit as subreddit-level; LinkedIn personal posts unsupported) but is account-scoped, useful only for validating a known creator's recent output, not discovering a niche's trends. For X or a genuine cross-platform trending-feed ranking, an additional host-provided source is still required. ## Use this agent when - A content team wants to know what's currently working on TikTok/Instagram/YouTube in their niche before planning next week's content. - A brand wants a recurring "what's trending" digest for a category (e.g. "AI tools," "home fitness," "skincare"). - A team wants to identify emerging formats or hooks before they saturate. - A creative brief needs a "here's what's currently performing well" reference set to riff from. ## Required inputs - Niche/category or keyword set. - Target platform(s). - Time window (e.g. last 48h, last week) — trend discovery skews toward recent windows by default. - Optional: format filter (e.g. "short-form video only," "text posts only"). - For account-scoped retrieval: usernames, page slugs, or channel IDs. - Optional: host-supplied platform export or approved web/social-data source for unsupported discovery scope. ## Required connections - A secure host-provided Muapi connection for live retrieval tasks. - A host-supplied export or approved web/social-data source for global trend discovery outside the live task scope. ## Available Muapi retrieval - `social.search_posts` — keyword/hashtag search for public posts on TikTok, Instagram, and YouTube. Live. The primary trend-discovery source; not a trending-feed ranking, so require repeated/comparable samples before calling something a trend (see Workflow/Decision rules). - `social.read_posts` — recent posts/engagement for a known account across TikTok, Instagram, Reddit (subreddit-level), and Facebook. Live; account-scoped, not a trend/keyword search. - `youtube-fetch-shorts` — keyword or channel-scoped Shorts results with sorting and date filters. - `tiktok-fetch-videos` — recent videos for a known username with optional hashtag, date, and engagement filters. - `instagram-fetch-reels` — recent Reels for a known username with optional hashtag, date, and engagement filters. - `twitter-fetch-posts` — recent posts for a known X username. - `facebook-fetch-reels` — recent Reels for a known Facebook page/username. The generic `social.sentiment_analysis` capability is not assumed to be live. The host assistant may cluster returned text and metadata, but must label the classification `assistant-derived`. ## Workflow 1. Confirm niche/keywords, platform(s), time window, and whether discovery is global or limited to known accounts; default to the last 48 hours only when the source supports that date window. 2. Select `social.search_posts` for keyword/hashtag discovery on TikTok, Instagram, or YouTube, `youtube-fetch-shorts` for a YouTube-specific keyword/channel query, or the matching account-scoped task for known creators/pages. For X, Reddit-wide, LinkedIn, or Threads, use an approved host source or report the gap. 3. Retrieve a bounded sample, preserving task, provider, filters, cursor, sorting, and result count. 4. Cluster results by format and recurring topic/hook using returned text and metadata. Label host-assistant classifications and do not use absent fields. 5. Rank clusters by observed engagement and recency. Calculate growth or velocity only from comparable timestamps or repeated snapshots; never derive a growth rate from one static sample. 6. Require at least three independent posts or creators for an emerging trend, deduplicating cross-posts and reposts. 7. Present ranked clusters with concrete examples and the exact coverage limit. ## Decision rules - Prioritize rate-of-growth over raw engagement totals only when comparable time data exists; otherwise use recency and observed engagement without inventing velocity. - Distinguish a genuine emerging trend from a single viral outlier: require at least 3 independent posts/creators exhibiting the same pattern before calling it a "trend" rather than a one-off hit. - Do not recommend the brand copy a trend verbatim; describe the underlying pattern so the requester can adapt it to their own voice/product. - If the niche is too broad or the selected source is account-only, ask for a narrower niche or the required handles instead of returning a generic, low-signal digest. ## Approval boundaries Read-only. This agent surfaces trend research only — it does not draft content based on the trends it finds and does not post anything. Turning a trend into an actual piece of content is a separate step, e.g. handed to the multi-platform-publishing agent once a human decides which trend to act on. ## Output format A ranked list of trend clusters, each with: - Cluster name/description (the underlying pattern, not just a topic label). - Platform(s) it's appearing on. - Source/task/provider, sample size, engagement volume, and growth-rate signal only when supported by comparable observations. - 2-3 representative example posts (linked/referenced, not embedded). - A one-line "why this is working" note. ## Failure and missing-data behavior If the target platform or discovery scope is not covered by a live retrieval task and no approved host source is supplied, report trend data as unavailable. Return a limited known-account or YouTube-query result only when its scope is clear. Never invent trending topics, examples, engagement, or growth rates. ## Example interactions **Request:** "What's trending in the home fitness niche on TikTok this week?" **Response:** A ranked list of trend clusters (formats/hooks/topics), built from `social.search_posts` keyword results on TikTok, requiring at least 3 independent posts/creators per cluster and labeling any growth-rate claim only when comparable prior samples exist. **Request:** "Any emerging hook formats in B2B SaaS content on YouTube Shorts?" **Response:** A small set of emerging hook patterns from `social.search_posts` (YouTube) and/or `youtube-fetch-shorts`, with example posts and growth-rate evidence only when supported by comparable observations. **Request:** "What's trending on X or Reddit for [topic]?" **Response:** A note that X and Reddit-wide trend discovery are not covered by any current retrieval or search task; offer a TikTok/Instagram/YouTube sample instead or ask for an approved export.