Browse documentation
On this page
Select the right workspace and advertising account
Resolve client workspaces and account IDs before reporting or making approved changes.
Try this in your assistant
In workspace [client name], list the Google and Meta accounts I can access. Show account names, IDs and currencies. Ask me to choose if there is more than one match. Do not change anything.
Resolve the client before the account
Start with the client workspace name. list_workspaces returns the workspaces available to the authenticated user, including roles and connections. resolve_workspace accepts a name or slug; ambiguous matches require a choice rather than selecting the first result.
Use the resolved workspace to discover accounts. A workspace is not an advertising account, and a manager account is not the serving Google Ads client. Confirm the exact account before asking for performance or a change.
Keep multi-account reports separate
Retrieve each account independently and label its account ID, currency and reporting period. Individual advertising tools support explicit account routing where available; choosing a target for a request does not need to change the dashboard selection.
Do not add revenue or spend across currencies without an explicit conversion method. Platform-attributed conversions can overlap, so a combined report is not a deduplicated attribution model.
Troubleshoot missing or ambiguous accounts
If the workspace cannot be resolved, list accessible workspaces and verify membership. If an expected advertising account is absent, check the platform login and its account permissions, then reconnect if necessary.
Never substitute another client account to get a successful response. Before a write, repeat the approved workspace, account and object IDs in the proposal.
Tool reference
Selected tools used in this guide. Names, descriptions and declared input fields are extracted from the MCP implementation. The connected assistant exposes the complete live schema, including field types, limits and account-routing options.
List client workspaceslist_workspaces
Lists every active PlugMind client workspace available to the authenticated user, including role and connected ad platforms. Call this before using ad tools when no exact workspace ID is known.
Declared input fields
No fields declared on this tool.
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
Resolve a client workspaceresolve_workspace
Resolves a client name or workspace slug to a stable workspace ID. If more than one workspace matches, returns the candidates instead of guessing.
Declared input fields
query
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
List Google Ads accountslist_google_ads_accounts
Lists Google Ads accounts connected to this PlugMind user and shows which account is selected.
Declared input fields
workspaceId
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
List Meta Ads accountslist_meta_ads_accounts
Lists Meta ad accounts owned by this authenticated PlugMind connection and shows which account is selected.
Declared input fields
workspaceId
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
Put it into practice
Multi-account advertising performance report
Prepare a client-by-client Google and Meta report with consistent dates, labeled currencies and clear next actions.
ExploreRelated documentation
Connect your first advertising account
Set up a PlugMind workspace, authorize Google or Meta, and verify a read-only report in your AI assistant.
ExploreRead advertising reports in context
Keep dates, currencies, attribution and missing data clear when comparing Google and Meta account performance.
Explore