mcp-playbooklisted

# Crevideo Reach MCP — Playbook > **Output language**: respond in the merchant's working language — Chinese for China-POP sellers (分级 / 真实抽成 / 触达阶梯 …), English for US sellers (tier / all-in take-rate / outreach waterfall …). Tool names stay identical in both. The **deep-reference layer** for the `crevideo-reach` MCP server. The MCP itself ships a baseline tool-map + typical flow via `SERVER_INSTRUCTIONS`; this skill covers what that baseline can't — the create flow, non-obvious constraints, and how to debug when behavior diverges from the brands-app UI. > **Source of truth**: if anything here disagrees with the **live tool list** in the running session, the **live tools win** (this doc can lag the MCP version). Only call tools that actually exist in the session; never assume historical or future tools. ## When NOT to use - Pure MCP-protocol or Claude-skill mechanics questions → wrong skill. - Nothing about automations, creators, affiliate analytics, TikTok Shop, or the reach area → don't invoke. ## Scope: affiliate (分销) only The MCP exposes **only affiliate/distribution** features. Campaign/marketing surfaces (campaign management, `/report/*` campaign reports, creator **marketplace** discovery, custom products, brand sampling) are **not** tools here — say they're out of scope. `query_*_performance` covers **collaboration / affiliate-product / shoppable-video** (affiliate), not campaign reports. There is **no** natural-language→filter and **no** copy-polish endpoint — **