Skip to main content
Glama

Server Details

Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
Synter-Media-AI/mcp-server
GitHub Stars
10
Server Listing
Synter MCP Server

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsC

Average 3.1/5 across 63 of 63 tools scored.

Server CoherenceA
Disambiguation3/5

The tool set has clear distinct purposes for many tools, such as performance pulls for different ad platforms (e.g., pull_google_ads_performance vs. pull_meta_ads_performance), but there is notable overlap and ambiguity in areas like 'execute' (a general-purpose tool that overlaps with many specific tools) and 'create_campaign_for_audience' vs. 'setup_google_ads_trial_funnel' (both create campaigns but with different scopes). Descriptions help differentiate, but the presence of broad tools like 'execute' and 'growth_run_pipeline' creates confusion about when to use them versus more specific alternatives.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., create_campaign_plan, list_audiences, pause_campaign), with clear and descriptive names. However, there are minor deviations, such as 'execute' (a single verb without a noun) and 'growth_discover' (noun_verb pattern), which break the overall consistency. The naming is largely predictable and readable, but these inconsistencies slightly detract from a perfect score.

Tool Count2/5

With 63 tools, the count is excessive for the server's purpose of advertising and campaign management. While the domain is broad, covering multiple ad platforms, analytics, and growth operations, the sheer number of tools makes the set feel heavy and potentially overwhelming. A more focused selection of 15-30 tools could better serve the scope without sacrificing functionality, as many tools are highly specific (e.g., separate performance pulls for each platform) or redundant (e.g., multiple TikTok-specific tools).

Completeness5/5

The tool surface is exceptionally complete for the advertising and growth domain, covering CRUD/lifecycle operations across campaigns, audiences, landing pages, and analytics. It includes creation (e.g., create_campaign_plan), management (e.g., enable_campaign, pause_campaign), analysis (e.g., forecast_campaign, get_attribution), and integration with external platforms (e.g., GA4, SimilarWeb). There are no obvious gaps; agents can perform end-to-end workflows from planning to execution and optimization without dead ends.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.