synter-ads
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.
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.
Tool Definition Quality
Average 3.1/5 across 63 of 63 tools scored.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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!
Your Connectors
Sign in to create a connector for this server.