🚧 Ad Studio MCP Agency Workflow Blockers Explained

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

Overview

If you are using the Ad Studio MCP (Model Context Protocol) to automate agency workflows, you may encounter limitations that affect multi-account analytics and creative deployment. This article explains what is happening and what to have ready when contacting our team.

What Is Happening

Customers using the Ad Studio MCP for agency workflows involving multiple ad accounts have reported gaps in analytics data and creative deployment functionality.

What This Affects

  • Multi-account analytics queries run through the MCP
  • Creative deployment tasks automated via MCP

What You Should Do Now

Because these are platform-level limitations rather than configuration issues, there are no self-serve steps that will fully resolve the gaps at this time. To get help as quickly as possible, please have the following ready when you contact our team:

  • The name of the ad account or accounts where you are experiencing the issue
  • A description of the specific MCP action or query that is producing unexpected results (e.g., analytics not returning, creative not deploying)
  • Any exact error messages or unexpected responses you have received
  • The approximate date and time when you first noticed the problem

Having this information ready will allow our team to investigate your specific case and escalate it appropriately.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.