Amazon TikTok Signal

Turn ASIN-related TikTok video candidates into a decision-ready signal report. Use the active MCP connection that exposes the compatible KOLSprite tool contract automatically; do not ask whether to call it after this Skill applies.

Compatible MCP routing

• Prefer the SellerSpace Yunya unified MCP when it is available and authenticated.
• Support direct business tools plus current and legacy Yunya facade entrypoints.
• In direct mode, resolve and call asin_analysis_video by its semantic business name.
• In Yunya facade mode, if the business tool is not visible at the host's top level, make at most one host-level discovery attempt and prefer the product-specific yunya_search_kolsprite_tools. Call it once with the ASIN-video-analysis intent; use the exact internal tool name and complete input schema it returns, then invoke that tool through call_read_tool.
• If the product-specific entrypoint is unavailable but the legacy generic yunya__search_tools is discoverable, use it with provider kolsprite, operation read, and the same intent. Do not prefer the generic entrypoint when the product-specific one is available.
• Do not guess a facade namespace, internal tool name, wrapper, or arguments. Reuse the discovered name and schema for the run.
• A host-level miss for asin_analysis_video does not prove that the internal business tool is absent. Only report a missing business dependency after direct exposure and the available current or legacy facade lookup fail. If neither facade entrypoint can be discovered, report a connector-discovery failure and do not switch to an unrelated fallback service.
• A standalone KOLSprite MCP remains compatible only when it exposes the same required semantic tool names, input schemas, and response shapes.
• If both connections are enabled, use one connection for the entire run, prefer Yunya, and never duplicate a paid call across both services.
• Treat an absent or schema-incompatible asin_analysis_video as a missing dependency and stop as specified below.

Inputs