synter-ads
Server Details
Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Synter-Media-AI/mcp-server
- GitHub Stars
- 17
- Server Listing
- synter-mcp-server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
7 tool updates
- Added
generate_image_ad - Added
generate_text_ad - Added
generate_ugc_ad - Added
generate_video_ad - Added
generate_voice_ad - Added
list_creative_assets - Added
upload_creative
1 tool update
- Changed
execute1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "title": "Result", - "type": "string" - } - }, - "required": [ - "result" - ], - "title": "executeOutput", - "type": "object" -}New value: +null
63 tool updates
- First observed
build_lookalike_audience - First observed
create_campaign_for_audience - First observed
create_campaign_plan - First observed
create_document - First observed
create_google_doc - First observed
create_google_sheet - First observed
create_landing_page - First observed
enable_campaign - First observed
execute - First observed
execute_campaign_plan - First observed
forecast_campaign - First observed
ga4_list_conversions - First observed
ga4_list_properties - First observed
ga4_run_report - First observed
get_attribution - First observed
get_connection_status - First observed
get_credit_balance - First observed
get_job_status - First observed
get_plan_execution - First observed
growth_discover - First observed
growth_enrich - First observed
growth_run_pipeline - First observed
list_audiences - First observed
list_available_scripts - First observed
list_campaigns - First observed
list_connected_accounts - First observed
list_skills - First observed
load_skill - First observed
measure_incrementality - First observed
optimize_budget - First observed
pause_campaign - First observed
publish_landing_page - First observed
publish_plan_document - First observed
pull_amazon_dsp_performance - First observed
pull_google_ads_performance - First observed
pull_linkedin_ads_performance - First observed
pull_meta_ads_performance - First observed
pull_microsoft_ads_performance - First observed
pull_reddit_ads_performance - First observed
pull_tiktok_ads_performance - First observed
pull_x_ads_performance - First observed
run_gaql_query - First observed
set_spend_alert - First observed
setup_custom_domain - First observed
setup_google_ads_trial_funnel - First observed
similarweb_analyze_domain - First observed
similarweb_compare_domains - First observed
similarweb_keyword_analysis - First observed
sync_audience - First observed
synter_onboarding_start - First observed
synter_onboarding_status - First observed
test_creatives - First observed
tiktok_ads_get_adgroup - First observed
tiktok_ads_get_campaign - First observed
tiktok_ads_get_insights - First observed
tiktok_ads_list_adgroups - First observed
tiktok_ads_list_ads - First observed
tiktok_ads_update_adgroup - First observed
update_campaign_budget - First observed
update_landing_page_html - First observed
upsert_plan_entity - First observed
verify_custom_domain - First observed
verify_pixel_ownership
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.
Run ads on Google, Meta, LinkedIn, TikTok and more from AI. 460+ tools across 14 platforms.
- adsOAuthcom.adspirer
Manage Google, Meta, Amazon, TikTok, LinkedIn & ChatGPT ads. 430 tools for campaigns & analytics.
AI marketing agent for Google Ads, Meta, GA4, TikTok, LinkedIn, Shopify, HubSpot and more.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceManage ad campaigns across Meta, Google, and TikTok, create campaigns, analyze performance, spy on competitors, and generate AI creatives.12MIT

PaidSync MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.MIT- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to create, analyze, and optimize ad campaigns across Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Amazon Ads, and ChatGPT Ads through natural language using 400+ tools.87MIT
- AlicenseNot gradedqualityBmaintenanceCreate, launch, and manage Meta + Google ads from Claude and ChatGPT. Analytics, strategy, and autopilot automation for any store.1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Multiple tools have overlapping or ambiguous purposes, causing confusion. For example, 'execute' is a catch-all that overlaps with many specific tools like 'create_campaign_for_audience' or 'execute_campaign_plan', and tools like 'list_connected_accounts' and 'get_connection_status' seem to serve similar connection-checking functions. The sheer number of tools exacerbates this issue, making it difficult for an agent to reliably choose the right one without extensive trial and error.
The naming is mixed with some patterns but inconsistent overall. There is a clear verb_noun pattern for many tools (e.g., 'create_campaign_plan', 'list_audiences'), but deviations like 'growth_discover' (noun_verb), 'synter_onboarding_start' (prefix_verb_noun), and 'execute' (single verb) break consistency. Additionally, some tools use underscores while others are more verbose, leading to a readable but not fully predictable naming scheme.
With 63 tools, the count is excessive for a coherent server scope, even for a comprehensive advertising platform. This bloated set includes many niche or redundant tools (e.g., multiple TikTok-specific tools and separate performance pull tools for each ad platform), which overwhelms the surface and suggests poor scoping. A more focused set of 15-30 tools would better serve the domain without sacrificing functionality.
The tool surface is highly complete for the advertising and growth domain, covering CRUD operations, analytics, forecasting, audience management, and integrations across multiple platforms. Minor gaps exist, such as no explicit tool for deleting campaigns or audiences, but agents can likely work around this using other tools like 'pause_campaign' or platform-specific actions. The breadth is impressive, though the depth in some areas (e.g., TikTok) might be overkill.