Skip to main content
Glama

Related Servers

Alternatives to mureo

  • A
    license
    A
    quality
    D
    maintenance
    Enables Claude to retrieve and analyze Google Analytics 4 data through 20+ analysis tools, providing insights on traffic, user behavior, conversions, and engagement metrics in Japanese-formatted output.
    20
    2
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables autonomous AI agents to safely inspect, optimize, and manage live search campaigns through 38 purpose-built tools covering bids, budgets, keywords, RSAs, assets, and negative keyword harvesting. Bundles two-layer Pydantic execution shields with bounded bid ceilings and fixed stepping, a preflight gatekeeper, and W3C distributed tracing that separates upstream Google Ads API latency from local execution overhead.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Lets AI clients like Claude and GPT query Google Ads performance data, inspect search terms and keywords, and take actions such as adding negative keywords, adjusting budgets and bids, and running account audits. It works out of the box with realistic demo data or connects to the live Google Ads API when credentials are supplied.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with unified marketing toolkits for SEO, GEO, paid media, and analytics, enabling audits, analysis, and approved changes across GA4, Search Console, Google Ads, Meta, X, LinkedIn, Reddit, TikTok, WordPress, and GoHighLevel.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to read and safely modify Google Ads campaigns, budgets, statuses, end dates, and negative keywords by diffing a reviewed desired-state file against live account state under policy-defined caps and single-use plan IDs. A scheduled guard can pause campaigns on spend thresholds while credentials and keys remain local.
    Apache 2.0

TDQS

A3.6/5.0

Scored across 229 tools

Disambiguation2/5

The surface contains many adjacent diagnostic and reporting tools: google_ads_performance_analyze, google_ads_cost_increase_investigate, google_ads_campaigns_diagnose, google_ads_health_check_all, the google_ads_monitoring_* family, and budget/search-term/RSA analysis tools all answer overlapping questions. Meta's analysis_* tools and insights_* tools similarly blur boundaries, so an agent must often choose among near-equivalent composite reads.

Naming Consistency3/5

Most names are snake_case with platform prefixes (google_ads_, meta_ads_, search_console_) and follow a resource_action pattern. However, families such as analysis_*, mureo_*, rollback_*, and creative_studio_* break the pattern, and some names are noun-first or awkwardly doubled, like meta_ads_ads_list.

Tool Count1/5

229 tools is extreme, far beyond the 3-15 well-scoped range and well past the 50+ threshold. Even for a broad cross-platform ad-ops domain, many tools are thin wrappers around overlapping reports or state bookkeeping, making the surface difficult to navigate.

Completeness4/5

Coverage is broad across Google Ads, Meta Ads, Search Console, state/rollback, and creative workflows, with core CRUD and lifecycle operations present for campaigns, budgets, ad groups, ads, keywords, audiences, catalogs, and diagnostics. Minor gaps remain, such as some delete/status operations being only implicit via update or absent, so the surface is not perfect.

Maintenance

ActivityActive
ResponsivenessResponsive