Skip to main content
Glama
Sign In
flin-linkedin-ads-mcp

flin-linkedin-ads-mcp

by flin-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to flin-linkedin-ads-mcp

No user-submitted related servers found.

    Related Servers

    • linkedin-ads-mcp

      dhawalshah
      A
      license
      B
      quality
      C
      maintenance
      LinkedIn Ads MCP server with full read/write campaign management, Ad Library competitive search, and Cloud Run team deployment.
      25
      6 npm
      MIT

    • HBCA Meta Ads MCP

      jmbrader
      F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for querying Meta Ads accounts through Meta's Marketing API. It provides tools to retrieve ad accounts, campaigns, ad sets, ads, and performance insights.
      -

    • google-marketing-mcp

      Bmiller4evr
      A
      license
      B
      quality
      D
      maintenance
      Read-only MCP server for Google Ads API, enabling natural language queries about campaigns, metrics, search terms, and change history without write access.
      6
      MIT

    • linkedin-campaign-manager-mcp

      ZLeventer
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the LinkedIn Marketing API — query campaigns, performance, and Lead Gen Forms from Claude in plain English. 19 read-only tools covering ad accounts, campaigns, creatives, performance analytics, demographics, video analytics, budget pacing, period comparisons, conversions, Lead Gen Forms, audiences, and targeting facets. Built for B2B paid social teams.
      19
      4
      -

    • Google Ads MCP Server

      MaxGhenis
      A
      license
      A
      quality
      F
      maintenance
      A read-write MCP server for managing Google Ads campaigns, ad groups, keywords, and ads via natural language.
      12
      24 PyPI
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (accounts, campaigns, groups, creatives, insights, ad library, partnerships). The only mild overlap is in the creative-content cluster (get_share_content, get_creative, get_creative_media), but descriptions clarify when to use each (metadata vs. media download vs. Posts resolution).

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (list_creatives, get_campaign, search_ad_library, get_insights). The two auth tools use a linkedin_ prefix (linkedin_login, linkedin_login_status) instead of a verb, a minor but readable deviation.

    Tool Count4/5

    16 tools is at the upper edge but each maps to a real LinkedIn Ads API surface (auth, accounts, campaigns, groups, creatives, insights, ad library, partnerships). No obviously redundant or filler tools, though the set is slightly heavy for a read-oriented server.

    Completeness3/5

    Read coverage is solid with list/get for accounts, campaigns, groups, creatives, and insights, plus auth and search. However, there are no create/update/pause/delete operations for campaigns or creatives, so write-side lifecycle management is a notable gap for an ads server.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources