Meta MCP integration for AI agents.
Connect AI agents to Meta through 4 structured actions, including get current user, get insights, and list ad accounts. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Meta integration exposes
The Meta Agent App exposes 4 provider-backed actions for marketing and social work. Its current contract lets an authorized agent retrieve the current meta graph api user for the connected access token, retrieve meta ads insights for an ad account, campaign, ad set, or ad object, and list meta ad accounts available to the connected access token. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Meta account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Meta capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADRetrieve the current Meta Graph API user for the connected access token.
get_insightsREADRetrieve Meta Ads insights for an ad account, campaign, ad set, or ad object.
INPUTS: objectId / level / fields / datePreset / timeRange
list_ad_accountsREADList Meta ad accounts available to the connected access token.
INPUTS: fields / limit / after / before
list_campaignsREADList campaigns under one Meta ad account with optional delivery status filters.
INPUTS: adAccountId / fields / limit / after / before
INPUT CONTRACTS
Know what the action needs before it runs.
get_insights
objectIdREQUIRED- A Meta Graph API object identifier.
levelOPTIONAL- The Meta insights aggregation level.
fieldsOPTIONAL- The comma-separated Meta fields or list of fields to request.
datePresetOPTIONAL- The Meta insights date preset.
timeRangeOPTIONAL- The custom Meta insights date range.
list_ad_accounts
fieldsOPTIONAL- The comma-separated Meta fields or list of fields to request.
limitOPTIONAL- The maximum number of records Meta should return.
afterOPTIONAL- The Graph API after cursor for requesting the next page.
beforeOPTIONAL- The Graph API before cursor for requesting the previous page.
list_campaigns
adAccountIdREQUIRED- The Meta ad account ID, with or without the act_ prefix.
fieldsOPTIONAL- The comma-separated Meta fields or list of fields to request.
limitOPTIONAL- The maximum number of records Meta should return.
afterOPTIONAL- The Graph API after cursor for requesting the next page.
beforeOPTIONAL- The Graph API before cursor for requesting the previous page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Retrieve the current Meta Graph API user for the connected access token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userVerify with Get Insights
Retrieve Meta Ads insights for an ad account, campaign, ad set, or ad object. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_insightsSAFETY BOUNDARY
Operate Meta with explicit limits
- Authorize Meta with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Meta data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Meta rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Meta task completed successfully.
CONNECTION MODEL
API key
Meta access token used with the Authorization: Bearer header. Create or view system user and app tokens in Meta Business Settings: https://business.facebook.com/latest/settings. The read-only Ads actions usually require permissions such as ads_read.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Meta.