meta-ads-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meta_ads_configureB | Meta Ads APIの接続設定を保存します |
| meta_ads_authenticateB | Meta Ads APIのOAuth認証を開始します。ブラウザでFacebookログインを行います。 |
| meta_ads_auth_statusA | Meta Ads APIの認証状態を確認します |
| meta_ads_server_infoA | MCPサーバーのバージョンと接続先情報を表示します |
| meta_ads_api_getC | Meta Ads APIにGETリクエストを送信します |
| meta_ads_api_postB | Meta Ads APIにPOSTリクエストを送信します（作成・更新兼用） |
| meta_ads_api_deleteC | Meta Ads APIにDELETEリクエストを送信します |
| meta_ads_api_list_pathsA | Meta Ads APIの既知エンドポイント一覧を表示します |
| meta_ads_save_tokenA | Graph API Explorerで取得したアクセストークンを保存します。short-livedトークンは自動的にlong-lived（60日有効）に交換されます。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct purpose: generic HTTP methods (GET, POST, DELETE), endpoint listing, authentication, configuration, and server info. No overlap between them.
All tools follow a consistent pattern with 'meta_ads_' prefix and underscore-separated names, e.g., meta_ads_api_get, meta_ads_authenticate.
With 9 tools, the set is well-scoped for an API wrapper: authentication, configuration, and basic CRUD via HTTP methods. Neither too few nor too many.
Covers essential operations: auth, config, and raw API calls (GET, POST, DELETE). However, it lacks higher-level abstractions for common ad operations, relying on users knowing endpoints.