菜单
Use for LidFly MCP v3 provider scope resolution: get_provider_context, resolve_campaign_scope, multi-account Yandex/VK/Avito/LidFly workflows, campaign lookup by name, and safe transfer of scope_arguments into call_tool/call_write_tool.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Work with Avito Ads through LidFly MCP v3: account discovery, campaigns, groups, budgets, statistics, agency/access/legal operations, 9-digit account_id validation, and read-preflight-write-reread guardrails.
Export advertising reports from Yandex Direct, Yandex Metrika, VK Ads, and Avito Ads through LidFly MCP v3 into connected Google Sheets, Google Docs, or Google Drive files, including verified tables and public creative images. Use when the user asks to export, save, append, or update advertising statistics in a Google file.
Build, audit, and optimize VK Ads campaigns through LidFly MCP v3 with connection_id/client_id provider context, manual VK user-filter limits, campaign scope resolution, creative preflight, statistics, and safe write workflows.
Build, audit, launch, and optimize Yandex Direct campaigns through LidFly MCP v3 with Wordstat, Metrika, provider context, resolve_campaign_scope, workspace_project_id, modern add_unified_campaign/add_responsive_ad workflows, and strict write guardrails.
Analyze Yandex Metrika through LidFly MCP v3: counter discovery, goals, UTM reports, Direct attribution, CPA/conversions, period comparisons, Workspace provider entities, and counter_id scope without client_login.
Work with Avito Ads through LidFly MCP v3: account discovery, campaigns, groups, budgets, statistics, agency/access/legal operations, 9-digit account_id validation, and read-preflight-write-reread guardrails.
| name | mcp-v3-provider-context |
| description | Use for LidFly MCP v3 provider scope resolution: get_provider_context, resolve_campaign_scope, multi-account Yandex/VK/Avito/LidFly workflows, campaign lookup by name, and safe transfer of scope_arguments into call_tool/call_write_tool. |
Use this helper before any provider task where the account, client, connection, campaign, or Workspace project is not already exact.
search_tools.get_tool_schema before the first call.get_provider_context({ provider, query? });resolve_campaign_scope({ provider, query, workspace_project_id? }).tool_args, scope_arguments, or next_call.arguments into the next provider call.call_tool; write with call_write_tool.client_login, client_id, account_id, counter_id, host_id, or connection_id from a human name.resolve_campaign_scope returns candidates, ask for the exact workspace_project_id or campaign id.workspace_project_id unless preflight returned one unambiguous scope.connection_id, optional client_login.counter_id, optional connection_id; no client_login.connection_id, optional client_id.connection_id, optional 9-digit account_id.webmaster_get_hosts, then host_id; no client_login.subdomain, site id, or store id from returned tool args.Tell the user which scope was selected in human terms and include the exact id only when useful for audit: workspace_project_id, provider account, campaign id. Do not expose tokens or secrets.