adpilot-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADPILOT_MOCK | No | Set to 1 to force mock mode alongside real adapters. | |
| ADPILOT_AUDIT_LOG | No | Path to the append-only JSONL audit log. | |
| ADPILOT_PROTECTED | No | Comma-separated campaign IDs that can never be changed or paused. | |
| META_ACCESS_TOKEN | No | The Meta access token. | |
| META_AD_ACCOUNT_ID | No | The Meta ad account ID. | |
| ADPILOT_MAX_CHANGE_PCT | No | The per-campaign change cap (default ±25%). | |
| ADPILOT_MAX_TOTAL_DAILY | No | The total daily spend ceiling. |
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 |
|---|---|
| list_campaignsB | List every campaign across connected ad platforms with status and daily budget. |
| campaign_performanceA | KPIs (spend, CTR, CPC, CPA, ROAS, CPM) per campaign over the last N days, ranked by ROAS. |
| detect_anomaliesB | Flag unusual moves in spend/CPA/ROAS/CTR/CPC using robust z-scores (median + MAD) against a trailing baseline. Returns the most severe first. |
| propose_budget_planA | Propose a reallocation of daily budgets toward higher-ROAS campaigns. Uses spend-weighted ROAS shrinkage and bounded water-filling. Nothing changes until apply_budget_plan is called. |
| apply_budget_planA | Execute a previously proposed budget plan. Plans expire and can only be applied once. |
| set_campaign_statusA | Pause or resume a single campaign. Protected campaigns are refused. |
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 6 tools
Each tool has a clearly distinct role: listing campaigns, measuring KPIs, detecting anomalies, proposing a plan, applying a plan, and changing status. The propose/apply pair is intentionally split and clearly differentiated by lifecycle stage.
All names use consistent snake_case, and most follow a verb_noun pattern such as list_campaigns, detect_anomalies, propose_budget_plan, and set_campaign_status. campaign_performance is the one minor deviation, using a noun phrase instead of a verb-led name.
Six tools is well-scoped for a focused ad budget optimization server. Each tool supports a distinct step in the workflow without obvious filler.
The surface covers the core workflow: inspect campaigns, measure performance, detect issues, propose and apply budget changes, and pause/resume campaigns. Minor gaps exist around inspecting or cancelling proposed plans and retrieving detailed campaign-level configuration.