Skip to main content
Glama
EfrainTorres

ArmaVita Meta Ads MCP

by EfrainTorres

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
META_APP_IDNoMeta App ID for local OAuth flow.
META_APP_SECRETNoMeta App Secret for local OAuth flow.
META_ACCESS_TOKENNoMeta access token for direct authentication (usually starts with EA...).
META_GRAPH_API_VERSIONNoMeta Marketing API version override (default is v25.0).v25.0

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_ad_accountsC

List ad accounts visible to a user context.

read_ad_accountC

Return account metadata for a single ad account.

list_adsD
read_adD
list_ad_previewsD
read_ad_creativeD
create_adD
list_ad_creativesD
read_ad_imageD
export_ad_image_fileD
update_adD
upload_ad_image_assetD
create_ad_creativeD
update_ad_creativeD
search_pagesD
list_account_pagesD
search_ads_archiveC

Search ads in Meta's public Ads Library endpoint.

list_ad_setsC

List ad sets under an account or campaign.

read_ad_setC

Fetch full details for one ad set.

create_ad_setC

Create an ad set under a campaign.

update_ad_setC

Update an ad set's delivery, budgeting, and targeting configuration.

create_campaign_budget_scheduleC

Create a high-demand budget schedule for a campaign.

list_campaignsC

List campaigns for an ad account with optional filters.

read_campaignC

Fetch detailed campaign metadata.

create_campaignC

Create a campaign with optional budgeting and bid controls.

update_campaignC

Update campaign settings for an existing campaign.

clone_campaignC

Duplicate a campaign using Meta's local Graph copy edge.

clone_ad_setC

Duplicate an ad set using Meta's local Graph copy edge.

clone_adC

Duplicate an ad using Meta's local Graph copy edge.

clone_ad_creativeC

Duplicate a creative using Meta's local Graph copy edge.

list_insightsC

Fetch insights for an account, campaign, ad set, or ad.

create_reportC

Generate OSS-local performance reports for Meta Ads accounts/campaigns.

search_web_contentC

Search through Meta Ads data and return matching record IDs.

read_web_contentC

Fetch complete record data by ID using cache-first + API fallback behavior.

search_interestsC

Find audience interests by keyword.

suggest_interestsC

Fetch related interests from a base list of interests.

estimate_audience_sizeB

Estimate audience size for targeting specs or validate deprecated interest-list mode.

search_behaviorsC

Search behavior-based targeting categories.

search_demographicsC

Search demographic targeting classes.

search_geo_locationsC

Search geo-location entities for targeting.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 40 tools

Disambiguation4/5

Most tools are clearly distinct, targeting specific resources like ads, creatives, ad sets, campaigns, and targeting categories. However, some tools like 'search_web_content' and 'read_web_content' have ambiguous boundaries with other search/read tools, and 'create_report' overlaps in purpose with 'list_insights' for performance data, which could cause mild confusion.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_ad', 'list_campaigns', 'read_ad_account', 'update_ad_set', 'search_interests', and 'clone_ad_creative'. There are no deviations in naming conventions, making the set predictable and easy to parse.

Tool Count2/5

With 40 tools, the count is excessive for the apparent scope of Meta Ads management. This many tools can overwhelm agents and increase complexity, as typical well-scoped servers have 3-15 tools. It suggests over-fragmentation of operations that could be consolidated.

Completeness5/5

The tool surface provides comprehensive coverage for the Meta Ads domain, including full CRUD operations for ads, creatives, ad sets, and campaigns, along with reporting, audience estimation, targeting searches, and asset management. There are no obvious gaps, enabling agents to handle complete workflows without dead ends.

Maintenance

ActivityStale
ResponsivenessNo issues