{"id":91530,"plugin_id":"plugin_asdk_app_6ad30793384c81919c4ff090fbeae35d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T18:09:22.230Z","digest":"231dbae04d9ab4366959f610cc40f99c87ff5ec85ddbc0609f8123d54acbd414","against":null,"payload":{"description":"Use AdNeuron to read stored Meta and Google Ads account and campaign reports, summarize performance, and rank campaign spend. This release is reporting-only.","included_files":[],"name":"adneuron-meta-workflow","skill_md_contents":"---\nname: adneuron-meta-workflow\ndescription: Use AdNeuron to read stored Meta and Google Ads account and campaign reports, summarize performance, and rank campaign spend. This release is reporting-only.\n---\n\n# AdNeuron reporting\nUse the configured remote MCP connection at https://mcp.adneuron.ai/mcp. Let the host complete OAuth sign-in and workspace selection. Never request passwords, tokens, or client secrets in chat. Request read-only access; never request or use write permissions for this release.\n\n## Scope\nRead stored data using documented tools. Discover current gateway catalogs before using a platform operation. Only use operations documented as read-only and currently available. This reporting-only package does not authorize platform connections, account synchronization, campaign or budget modifications, publishing, billing changes, or scheduled tasks, even if the server exposes such tools. Explain that those actions are outside this release. Do not use another integration to perform them under this plugin.\n\n## Workflow\n- Use list_accounts to resolve actual account IDs and their platform, currency, source, timezone, connection state and freshness. Respect the host-selected authenticated connection. An email in a prompt does not select an account or prove identity. If returned data contradicts the requested workspace, stop and ask the user to select the correct connection in the host.\n- Use get_performance_summary for account and platform reports, with supported lookback_days values 7, 30, 60 or 90.\n- Use list_top_performers for spend rankings; specify sort_by=spend and the requested limit and lookback_days. This is a spend ranking, not evidence of business effectiveness.\n- Use meta_ads and google_ads with action=list_tools to discover available read operations and argument contracts. Execute only necessary read operations against returned IDs.\n- For Meta campaigns, list_campaigns and get_campaign_performance can return stored status, budget and metrics.\n- For Google campaigns, resolve campaign IDs from returned stored listings and use get_campaign_detail. A top-N result is not necessarily a complete campaign inventory; disclose coverage limits.\n\n## Reporting integrity\nUse exact tool-returned complete account-local dates excluding today. Show dates, timezone, currency and data source. A lookback count alone does not establish exact date boundaries. If boundaries are absent, explicitly state that period alignment is unverified; do not silently supply assumed dates.\nDistinguish recorded zero from null, missing or unverified metrics. Preserve unavailable Meta conversions and conversion value; do not invent mapping or report a complete combined conversion total when any included outcomes are unavailable.\nAggregate only compatible currencies and identical reporting windows. Withhold mixed-currency totals rather than implicitly converting. Platform conversions may measure different outcomes and do not establish comparable customers, revenue or attribution.\nLabel sample/fictional records from returned source flags and never describe them as provider-synced live results. No provider sync timestamp is not evidence of fresh live data.\nReconcile campaign/account totals only for the same dates, scope and currency. Disclose excluded campaigns, incomplete coverage or differences. Do not alter values to force reconciliation.\nIf impressions are zero, CTR is undefined/not meaningful even if the server returns zero. If conversions are unavailable or zero, do not present a meaningful CPA. Do not invent causal explanations, optimization claims or revenue.\nState no changes were made only when no mutating operations were called.\n\n## Boundaries\nFor a nonexistent campaign, report no match without substitution or invented performance. Unsupported platforms such as TikTok are not represented by Google or Meta data. Customer email sending and other unrelated actions are unavailable through this plugin. Clearly distinguish a written draft from a sent message.\nOn tool failure, describe the actual error and affected scope. Do not claim successful authentication, complete reporting, server-side read-only enforcement, or validation without supporting evidence.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}