Skip to main content
Glama
bitscorp-mcp

Adjust MCP

by bitscorp-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Adjust MCP

No user-submitted related servers found.

    Related Servers

    • meta-ads-mcp-server

      jonathanposovatz
      A
      license
      A
      quality
      D
      maintenance
      MCP Server for the Meta Marketing API. Gives Claude Desktop direct access to your ad account data — campaign performance, creative analysis, audience breakdowns, and budget pacing.
      10
      151 npm
      1
      MIT

    • meta-ads-mcp

      fujioka0729
      A
      license
      A
      quality
      D
      maintenance
      MCP server to manage Meta Ads (Facebook/Instagram) campaigns, ad sets, insights, and audiences from Claude Code using natural language.
      9
      3 npm
      MIT

    • google-ads-mcp

      aisandler
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Ads campaign reporting and management via Claude, enabling GAQL queries, performance metrics, and campaign modifications.
      20 npm
      MIT

    • Meta Ads MCP Server

      brmh
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for managing and analyzing Meta Ads (Facebook/Instagram) with over 80 natural-language tools for AI agents like Claude Desktop.
      -

    • Meta Ads MCP

      gorossesolutions
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes Meta Marketing API to Claude, enabling analysis and management of Facebook/Instagram ad accounts, including campaigns, insights, and budget adjustments with safety confirmations.
      1,040 npm
      MIT
    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

    C2.2/5.0

    Scored across 2 tools

    Disambiguation3/5

    The two tools have overlapping purposes related to Adjust reporting, which creates some ambiguity. 'adjust-reporting' is vague and could encompass standard reports, while 'adjust-standard-report' is more specific but may be a subset of the first tool. Descriptions help differentiate them, but the boundaries are not entirely clear.

    Naming Consistency4/5

    Tool names follow a consistent pattern with 'adjust-' prefix and snake_case style, making them predictable and readable. There is a minor deviation in that one tool uses a hyphenated compound word ('reporting') while the other uses an underscore ('standard_report'), but overall the naming is mostly consistent.

    Tool Count2/5

    With only 2 tools, the server feels too thin for a reporting domain, as it lacks basic operations like filtering, customization, or data export. This minimal set is insufficient for comprehensive reporting workflows, making it borderline inappropriate for the apparent scope.

    Completeness2/5

    The tool surface has significant gaps for a reporting server. It lacks essential operations such as creating custom reports, updating report parameters, deleting reports, or accessing detailed analytics beyond standard metrics. This incompleteness will likely cause agent failures in handling varied reporting tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources