Ad platforms and their tools
The ad platforms Pilot MCP serves, their read-only tools, and what is never served.
Pilot MCP currently serves 4 ad platforms, read-only: Google Ads, Meta Ads, Google Analytics 4 and Google Search Console. Your assistant only sees the platforms connected to your workspace and included in your plan: your workspace console shows them.
With all 4 platforms connected, your assistant receives 157 tools. None of them changes a campaign, a budget or a setting.
Served tools
| Platform | Tool prefix | Read-only tools |
|---|---|---|
| Google Ads | google_ | 66 |
| Meta Ads | meta_ | 44 |
| Google Analytics 4 | google_analytics_ | 35 |
| Google Search Console | google_search_console_ | 5 |
| Search and Pilot analyses | search, fetch, pilot_ | 7 |
Each platform page lists its tools by family, with their parameters, as the server serves them to your assistant.
What Pilot MCP never serves
Some connector tools stay out of the MCP server, whatever your plan and whatever your role. For the served platforms, here are the families removed and why.
Secrets and authentication tokens
These tools return a token or the value of a secret in clear text. Pilot keeps the access to your ad platforms in an encrypted vault and never shows it to an assistant.
Removed tools: google_analytics_create_measurement_protocol_secret, google_analytics_get_measurement_protocol_secret, google_analytics_google_auth_exchange, google_analytics_google_auth_refresh, google_analytics_google_auth_url, google_analytics_list_measurement_protocol_secrets.
Ad platform billing
Reading the invoices or payment setup of an account is not advertising management, and some of these tools commit to a commercial act.
Removed tools: google_get_billing_setup, meta_get_account_billing_info.
Personal data of your customers
Customer lists, leads and user-level exports: sending this data to a third-party model would go beyond the consent your customers gave.
Removed tools: google_analytics_create_audience_export, google_analytics_query_audience_export, google_create_customer_match_list, google_upload_customer_match_data, meta_upload_customer_list.
Agency portfolio and accounts outside the workspace
These tools list every account, page, pixel or catalogue an access can see, far beyond the accounts attached to your workspace, or read pages, leads and studies that Pilot cannot match to any account of your workspace. Pilot only serves what is attached.
Removed tools: google_analytics_get_account, google_analytics_list_accounts, meta_get_ad_study, meta_get_agencies, meta_get_business, meta_get_business_overview, meta_get_client_ad_accounts, meta_get_instagram_accounts, meta_get_leadgen_leads, meta_get_leadgen_test_leads, meta_get_owned_ad_accounts, meta_get_owned_pages, meta_get_owned_pixels, meta_get_page, meta_get_partners, meta_get_reach_frequency_prediction, meta_list_ad_studies, meta_list_business_apps, meta_list_businesses, meta_list_leadgen_forms, meta_list_product_catalogs.
Writes whose target is outside the scope
These writes target an object that Pilot cannot match to an account of your workspace (a Business Manager, a page, a shared pixel). They are never served, even when a plan opens writes.
Removed tools: google_analytics_create_firebase_link, google_analytics_create_google_ads_link, google_analytics_create_property, google_create_test_account, meta_create_ad_account, meta_create_custom_conversion, meta_create_leadgen_form, meta_delete_leadgen_form, meta_send_conversion_events, meta_update_pixel.
Account access management
Granting a role on an account or a property, admin included, or removing someone, is not campaign management. It is done in the ad platform itself.
Removed tools: google_analytics_create_access_binding, google_analytics_delete_access_binding, google_analytics_update_access_binding, meta_add_account_user, meta_remove_account_user.
Tools with no use for an assistant
An internal state shared by every workspace, a report no tool can read back, a setting specific to the Pilot instance: nothing useful for you.
Removed tools: meta_create_insights_async_job.
Reads the offer does not serve
The Pilot MCP offer does not serve these reads either, which full Pilot keeps: the payment methods and transactions of a Meta account, the people and accesses of a Meta account or a Google Analytics property, and the preview of a Meta ad, being repaired. They are not needed to read performance, and two of them touch payment data.
Removed tools: google_analytics_get_access_binding, google_analytics_list_access_bindings, google_analytics_run_access_report, meta_get_ad_preview, meta_get_funding_source, meta_get_transactions, meta_list_account_users.
Your mailboxes and documents
Pilot MCP never serves personal connectors, even when you connected them in Pilot: Google Workspace, Gmail, Google Drive, Microsoft 365, Outlook, OneDrive and Google Workspace & Marketing. Their content (emails, documents, calendars) has no place in an offer that reads ad platforms.
How this reference is produced
These pages are not written by hand. A generator builds the Pilot MCP server in memory, for a mock workspace of the Pilot MCP offer, on the initial plan, where every Pilot platform is connected, and reads the list of tools it serves (tools/list), as MCP server directories do: the server itself keeps the platforms and analyses of the offer. The generator makes no network call and reads no real data. Last generated from the Pilot application at commit e60071144c97.