Marketing Ops 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_funnelC | Calculate explicit-denominator conversion and acquisition metrics for one cohort. |
| reconcile_transactionsC | Compare exact transaction IDs only when declared attribution scopes match. |
| design_experimentB | Estimate a fixed-horizon two-proportion experiment sample size. |
| analyze_experimentB | Review a completed fixed-horizon experiment with sample-ratio and approximation gates. |
| build_campaign_urlB | Build a normalized UTM URL while preserving unrelated parameters. |
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 5 tools
Each tool targets a distinct operation: funnel math, transaction reconciliation, experiment sizing, experiment review, and UTM construction. design_experiment vs analyze_experiment are clearly separated by lifecycle stage (pre-run sizing vs post-run review), leaving no realistic misselection risk.
All five tools follow a consistent snake_case verb_noun pattern (calculate_, reconcile_, design_, analyze_, build_). The convention is uniform and the verbs accurately signal the action type.
Five tools is on the lean side but each maps to a genuinely distinct analytical task with no filler. The surface is well-scoped, though it sits at the low end of what a marketing-ops server might warrant.
The set covers a coherent core: funnel conversion, transaction reconciliation, the full experiment lifecycle (design plus analysis), and campaign URL construction. Gaps exist around data ingestion, cohort/segment definition, and results export or reporting, but core workflows are workable.