executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
trend-spotterIdentify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score.
Independent GitHub snapshot · Automated classification · Original documentation governs
Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score. Read the API map before selecting a capability.
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.
twitter_web_trendingtiktok_app_v3_home_feedyoutube_web_v2_general_searchgoogle_news_bulk_articlesreddit_app_popular_feedweibo_web_hot_searchsandbase_discover, then inspect the returned name with sandbase_inspect to confirm the schema and pricing.execute_as with sandbase_run; collect async results with sandbase_run_get as described above.sandbase_inspect before using any capability.