ops-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADTECH_ROLE | Yes | Role identifier passed as X-Role header to backend services | |
| ADTECH_USER | Yes | User identifier passed as X-User header to backend services | |
| ADTECH_TENANT | Yes | Tenant identifier passed as X-Tenant header to backend services |
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 |
|---|---|
| lpb_list_pagesA | 列出落地页（读）。来源 lpb mock-server 页面管理。 |
| lpb_get_pageA | 获取单个落地页详情（读）。 |
| lpb_create_pageA | 创建落地页（写，需 confirm）。body 为页面字段，交由 lpb mock-server 落库。 |
| lpb_update_pageA | 更新落地页（写，需 confirm）。按 id 更新字段。 |
| lpb_delete_pageA | 删除落地页（写，需 confirm，破坏性操作请格外确认）。 |
| adtech_list_campaignsA | 列出 campaign（读）。来源 ad-tech-labs media-adapter（带租户隔离）。 |
| adtech_adjust_bidA | 调整 campaign 出价/预算（写，需 confirm）。经 media-adapter 预算门禁 + 审计。 |
| adtech_launch_campaignA | 一句话起投 campaign（写，需 confirm）。复用 ad-tech-labs launch 的 NL→campaign 能力（M4 合流点）。 |
| adtech_set_campaign_statusA | 停投/恢复 campaign（写，需 confirm）。active=恢复投放，paused=停投。 |
| system_query_auditB | 查询本 MCP 的操作审计日志（读，仅限内部）。 |
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 10 tools
Each tool targets a distinct action on a distinct resource: adtech tools manage campaigns (status, bids, launch, list), lpb tools handle landing pages with full CRUD, and system_query_audit is separate. No two tools perform the same operation on the same resource.
Tool names follow a consistent pattern of prefix_verb_noun: adtech_* for campaign operations, lpb_* for landing page operations, and system_* for audit. All verbs are clear and parallel (list, get, create, update, delete, set, adjust, launch).
With 10 tools total, the set is well-scoped and not excessive. It covers two domains (adtech and landing pages) plus a system utility, each with a manageable number of operations that fit within the typical 3-15 range.
The landing page surface is complete with CRUD (list, get, create, update, delete). The adtech surface covers list, status changes, bid adjustments, and launch, but lacks a dedicated single-campaign get/read operation (though list may suffice) and no delete/stop operation beyond status changes. Overall, the core workflows are well covered.