Run1Ads: live Meta ads consultant

Live Meta ads consultant for e-commerce. Checks ads, Pixel and store hourly, then gives the one fix.

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
86%
命名の品質
97%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~2,956トークン数(ツール定義)
~810 B一般的なレスポンスサイズ
注意への影響は大きい(128k コンテキストの 2.31%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "consultant": {
      "url": "https://run1ads.ai/mcp/rpc"
    }
  }
}

リモートエンドポイント

https://run1ads.ai/mcp/rpcstreamable-http

できること

ツール一覧

ツール(15)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢list_brands

List the brands this Run1Ads account can open, with each brand id, name and whether Meta is connected. Use it first when the user manages more than one brand or names a brand, then pass brand_id to the other tools. Every other tool uses the most recently updated brand when brand_id is left out.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_today(brand_id)

Start here for "what should I do today?" or "what's wrong with my Meta ads?". Returns today's brief: the one fix to do first, other findings ranked by buyers lost (each with its item_key, the number behind it and exact steps), what changed, what is working and the live check status. It summarises the other tools; use get_performance for full numbers, get_live_alerts for every alert, get_sales_funnel for each funnel step. Also returns the Today screen: needs_you_now (critical live alerts, shown first), the headline (for example "3 fixes could lift your ROAS from 1.9x to about 2.6x", all estimates) and up to 3 fixes with problem, fix and worth. Pass an item_key to add_to_fix_list or send_paused_draft. Saved data from the latest hourly check.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_performance(brand_id)

Use for questions about results and goals: "what's my ROAS?", "how much did I spend?", "am I on track this month?". Returns saved Meta ads totals (spend, revenue, ROAS, purchases, click rate, cost per click, frequency) and this month's ROAS goal with the gap to it. For where buyers drop out use get_sales_funnel; for per ad tiredness use get_ad_fatigue. Saved data, refreshed by the hourly check.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_sales_funnel(brand_id)

Use for "where am I losing buyers?" or "people click but don't buy". Returns each step from ad click to purchase as how many in 1,000 move on, the e-commerce benchmark per 1,000, above or below, the trend, and which step loses the most buyers. For totals like spend and ROAS use get_performance; for why visitors leave the store use get_store_checks. Saved data, refreshed by the hourly check.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_live_alerts(brand_id, include_resolved)

Use for "is anything broken right now?" or "any alerts?". Returns when the hourly live check last ran, today so far, open alerts with critical first (for example spend with no sales, a rejected ad, a broken Pixel or store) and, unless include_resolved is false, alerts resolved in the last 7 days. Each alert says why it matters and how to fix it. get_today shows only the top items; this shows them all. Saved data, checked every hour.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "include_resolved": {
      "type": "boolean",
      "default": true,
      "description": "Include alerts resolved in the last 7 days."
    }
  },
  "additionalProperties": false
}
🟢get_store_checks(brand_id)

Use for questions about the store and tracking, not the ads: "is my Pixel working?", "does my store work in the Instagram browser?", "why do visitors from my ads leave?". Returns whether the store works inside the Instagram and Facebook app browser, whether Add to Cart shows on mobile, whether the Meta Pixel fired, five store scores out of 100, the weakest product pages, and this week's problems for visitors from Meta ads (taps that do nothing, page errors, where they leave, slow pages) with fix steps. For funnel rates use get_sales_funnel. Saved data from the latest daily store walk and weekly visitor review.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_ad_fatigue(brand_id)

Use for "which ads are getting tired?" or "should I refresh my creative?". Returns each ad's frequency, click rate and its change, and hook rate, highest frequency first, so you can see which ads people have seen too often. For the copy and video content itself use get_ad_copy_review; for account totals use get_performance. Saved data, refreshed by the hourly check.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_ad_copy_review(brand_id)

Use for "is my ad copy good?" or "why do viewers skip my video?". Returns a review of ads already running: first line, headline, call to action and link, with a score and specific issues, plus video ads from the last 7 days with hook rate, hold rate, where viewers drop off, a visual review of the frames and fix steps. For which ads are tired use get_ad_fatigue. Saved data from the latest review.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_audiences(brand_id)

Use for "who is buying?", "which placement works best?" or "is my custom audience big enough?". Returns buyers in the period, saved custom audiences with size and whether each is big enough to deliver, and results split by placement (Instagram, Facebook, Reels, Stories). For overall ROAS use get_performance; for funnel drop offs use get_sales_funnel. Saved data from the latest Meta read.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_competitor_changes(brand_id)

Use for "what are my competitors doing?". Returns recent changes in the brand's chosen competitors' Meta ads: who changed what (number of ads, angle, format) and when. Competitors are set in the Run1Ads app. Saved data, refreshed weekly.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    }
  },
  "additionalProperties": false
}
🟢get_fix_list(brand_id, status)

Use for "what have I committed to?" or "did my fix work?". Returns the fixes the user chose to do, filtered by status (open, done or all, default all), each with its fix_id and, once newer data is saved, whether the tracked number moved after the fix was marked done. Use the fix_id with mark_fix_done. For new findings use get_today.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "done",
        "all"
      ],
      "default": "all"
    }
  },
  "additionalProperties": false
}
🟡add_to_fix_list(brand_id, item_key, title, why, how, ...)

Add a fix to the brand's Run1Ads fix list. Pass item_key from get_today to add that finding with its steps and the number to track, or pass your own title. Writes to Run1Ads only. Nothing changes in Meta or on your store.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "item_key": {
      "type": "string",
      "description": "The key of a finding from get_today (for example vc_atc or fatigue)."
    },
    "title": {
      "type": "string",
      "maxLength": 300,
      "description": "Your own fix title, if not using item_key."
    },
    "why": {
      "type": "string",
      "maxLength": 1000
    },
    "how": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 8,
      "description": "Steps to apply it."
    },
    "pillar": {
      "type": "string",
      "description": "funnel, journey, fatigue, content, audience, strategy or general."
    }
  },
  "additionalProperties": false
}
🟢mark_fix_done(brand_id, fix_id)

Mark a fix on the fix list as done. Run1Ads records the number at that moment so it can show whether the fix worked once newer data is saved. Writes to Run1Ads only.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "fix_id": {
      "type": "integer",
      "description": "The fix id from get_fix_list."
    }
  },
  "required": [
    "fix_id"
  ],
  "additionalProperties": false
}
🟢ask_consultant(brand_id, question)

Ask the Run1Ads consultant a question about this brand in plain English. It answers from the saved account data only, with exact steps you can apply. It advises only and never changes anything. Up to 10 questions per brand per day, shared with the app.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "question": {
      "type": "string",
      "minLength": 3,
      "maxLength": 1000
    }
  },
  "required": [
    "question"
  ],
  "additionalProperties": false
}
🟡send_paused_draft(brand_id, item_key, objective, daily_budget_usd, confirm)

Send one finding from get_today to the brand's own Meta ad account as a PAUSED campaign and ad set, so you can finish and switch it on yourself in Ads Manager. Nothing spends. Only findings marked draftable can be sent. Only use this when the user has clearly asked for it, and pass confirm true. Without confirm it returns a preview and sends nothing.

入力スキーマ

{
  "type": "object",
  "properties": {
    "brand_id": {
      "type": "string",
      "description": "Brand id from list_brands. Leave it out to use your most recently updated brand."
    },
    "item_key": {
      "type": "string",
      "description": "The key of a draftable finding from get_today (fatigue, creative_copy, placement or lookalike)."
    },
    "objective": {
      "type": "string",
      "enum": [
        "sales",
        "traffic"
      ],
      "default": "sales"
    },
    "daily_budget_usd": {
      "type": "number",
      "minimum": 1,
      "maximum": 500,
      "default": 10,
      "description": "Daily budget saved on the paused draft. It does not spend until you switch the draft on."
    },
    "confirm": {
      "type": "boolean",
      "description": "Must be true, and only after the user explicitly asked to send this draft."
    }
  },
  "required": [
    "item_key"
  ],
  "additionalProperties": false
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 15 件