@cesteral/dbm-mcp 1.0.0

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.js

@@ -0,0 +1,170 @@
+export const crossPlatformPerformancePrompt = {
+    name: "cross_platform_performance_comparison",
+    description: "Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.",
+    arguments: [
+        {
+            name: "dateRange",
+            description: "Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)",
+            required: false,
+        },
+    ],
+};
+export function getCrossPlatformPerformanceMessage(args) {
+    const dateRange = args?.dateRange || "LAST_7_DAYS";
+    return `# Cross-Platform Performance Comparison
+
+Date Range: \`${dateRange}\`
+
+This workflow coordinates across multiple MCP servers to gather, normalize, and compare campaign performance. You must be connected to all relevant servers.
+
+---
+
+## Step 1: Gather Metrics from Each Platform
+
+### DV360 (via dbm-mcp)
+
+\`\`\`json
+{
+  "tool": "dbm_get_performance_metrics",
+  "params": {
+    "campaignId": "{dv360CampaignId}",
+    "advertiserId": "{dv360AdvertiserId}",
+    "dateRange": "${dateRange}"
+  }
+}
+\`\`\`
+
+Key metrics returned: impressions, clicks, spend, CPM, CTR, CPA, ROAS.
+
+### The Trade Desk (via ttd-mcp)
+
+\`\`\`json
+{
+  "tool": "ttd_get_report",
+  "params": {
+    "reportName": "Cross-Platform Comparison",
+    "dateRange": "${dateRange}",
+    "dimensions": ["CampaignId", "CampaignName"],
+    "metrics": ["Impressions", "Clicks", "TotalCostAdvertiserCurrency", "Conversions", "Revenue"],
+    "advertiserIds": ["{ttdAdvertiserId}"]
+  }
+}
+\`\`\`
+
+### Google Ads (via gads-mcp)
+
+\`\`\`json
+{
+  "tool": "gads_get_insights",
+  "params": {
+    "customerId": "{gadsCustomerId}",
+    "entityType": "campaign",
+    "dateRange": "${dateRange}"
+  }
+}
+\`\`\`
+
+### Meta Ads (via meta-mcp)
+
+\`\`\`json
+{
+  "tool": "meta_get_insights",
+  "params": {
+    "entityId": "{metaCampaignId}",
+    "fields": ["impressions", "clicks", "spend", "cpm", "ctr", "cpc", "conversions", "cost_per_action_type"],
+    "datePreset": "last_7d"
+  }
+}
+\`\`\`
+
+---
+
+## Step 2: Normalize Metrics
+
+Each platform reports metrics differently. Normalize to a common format:
+
+| Metric | DV360 (dbm-mcp) | TTD (ttd-mcp) | Google Ads (gads-mcp) | Meta (meta-mcp) |
+|--------|-----------------|---------------|----------------------|-----------------|
+| **Spend** | USD (from report) | Advertiser currency | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CPM** | Calculated | Calculated | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CPC** | Calculated | Calculated | Micros (÷ 1,000,000) | Cents (÷ 100) |
+| **CTR** | Ratio (0-1) | Ratio (0-1) | Ratio (0-1) | Percentage string |
+| **Conversions** | Bid Manager metric | \`Conversions\` field | \`conversions\` metric | \`conversions\` field |
+
+### Normalization formulas:
+
+- **Google Ads micros → USD**: Divide by 1,000,000
+- **Meta cents → USD**: Divide by 100
+- **Meta CTR string → number**: Parse "1.23%" to 0.0123
+- **CPM**: (Spend / Impressions) × 1,000
+- **CTR**: Clicks / Impressions
+- **CPA**: Spend / Conversions
+- **ROAS**: Revenue / Spend
+
+---
+
+## Step 3: Compare in Normalized Table
+
+Present results in a unified format:
+
+| Platform | Campaign | Impressions | Clicks | CTR | Spend (USD) | CPM (USD) | CPA (USD) | ROAS |
+|----------|----------|-------------|--------|-----|-------------|-----------|-----------|------|
+| DV360 | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| TTD | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| Google Ads | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+| Meta | {name} | {n} | {n} | {%} | \${n} | \${n} | \${n} | {n}x |
+
+---
+
+## Step 4: Identify Winners and Losers
+
+Rank platforms by key efficiency metrics:
+
+### By CPA (lower is better)
+1. Best CPA platform → candidate for budget increase
+2. Worst CPA platform → candidate for budget decrease or pause
+
+### By ROAS (higher is better)
+1. Best ROAS platform → highest return on investment
+2. Worst ROAS platform → losing money if < 1.0
+
+### By CPM (context-dependent)
+- Low CPM + low CTR → cheap but ineffective (awareness only)
+- High CPM + high CTR → expensive but effective (consider if CPA is good)
+
+---
+
+## Step 5: Recommend Budget Reallocation
+
+Based on the comparison, suggest budget moves:
+
+### Conservative Approach (low risk)
+- Shift 10-15% of budget from worst performer to best performer
+- Monitor for 1 week before making further changes
+
+### Aggressive Approach (high confidence)
+- Shift 25-30% of budget from worst performer to best performer
+- Pause campaigns on platforms with ROAS < 0.5
+
+### Execution
+
+For each platform where budget changes are needed:
+
+- **DV360**: Use \`dv360_update_entity\` (via dv360-mcp) to adjust IO/Line Item budgets
+- **TTD**: Use \`ttd_update_entity\` (via ttd-mcp) to adjust campaign/ad group budgets
+- **Google Ads**: Use \`gads_update_entity\` (via gads-mcp) to adjust campaign budgets
+- **Meta**: Use \`meta_update_entity\` (via meta-mcp) to adjust campaign/ad set budgets
+
+---
+
+## Gotchas
+
+- **Date ranges differ by platform**: DV360 uses Bid Manager presets (LAST_7_DAYS), TTD uses date strings, Google Ads uses date ranges in GAQL, Meta uses datePreset or timeRange. Align dates carefully.
+- **Currency differences**: Ensure all platforms report in the same currency before comparing. TTD reports in advertiser currency, others in USD by default.
+- **Attribution models differ**: Each platform attributes conversions differently. Cross-platform CPA comparisons are directional, not exact.
+- **Data freshness varies**: Meta has up to 48-hour lag. DV360 reports are async. TTD and Google Ads are near-real-time. Compare data from the same time window.
+- **Impression counting differs**: Viewability standards vary by platform. CPM comparisons should account for this.
+- **Not all campaigns are comparable**: Only compare campaigns targeting similar audiences, geos, and objectives. A brand awareness campaign on DV360 shouldn't be compared with a direct response campaign on Google Ads.
+`;
+}
+//# sourceMappingURL=cross-platform-performance.prompt.js.map

package/dist/mcp-server/prompts/definitions/cross-platform-performance.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cross-platform-performance.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/cross-platform-performance.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,8BAA8B,GAAW;IACpD,IAAI,EAAE,uCAAuC;IAC7C,WAAW,EACT,mOAAmO;IACrO,SAAS,EAAE;QACT;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EACT,0FAA0F;YAC5F,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,kCAAkC,CAAC,IAA6B;IAC9E,MAAM,SAAS,GAAG,IAAI,EAAE,SAAS,IAAI,aAAa,CAAC;IAEnD,OAAO;;gBAEO,SAAS;;;;;;;;;;;;;;;;oBAgBL,SAAS;;;;;;;;;;;;;;oBAcT,SAAS;;;;;;;;;;;;;;;;oBAgBT,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0G5B,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/custom-query-workflow.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "./types.js";
+export declare const customQueryWorkflowPrompt: Prompt;
+export declare function getCustomQueryWorkflowMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=custom-query-workflow.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/custom-query-workflow.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"custom-query-workflow.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/custom-query-workflow.prompt.ts"],"names":[],"mappings":"AASA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAEzC,eAAO,MAAM,yBAAyB,EAAE,MAiBvC,CAAC;AAEF,wBAAgB,6BAA6B,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAmJnF"}

package/dist/mcp-server/prompts/definitions/custom-query-workflow.prompt.js

@@ -0,0 +1,164 @@
+export const customQueryWorkflowPrompt = {
+    name: "custom_query_workflow",
+    description: "Step-by-step guide for building custom Bid Manager queries with the dbm_run_custom_query tool",
+    arguments: [
+        {
+            name: "advertiserId",
+            description: "DV360 Advertiser ID to query",
+            required: true,
+        },
+        {
+            name: "queryGoal",
+            description: "What you want to analyze (e.g., 'campaign performance', 'device breakdown', 'video metrics')",
+            required: false,
+        },
+    ],
+};
+export function getCustomQueryWorkflowMessage(args) {
+    const advertiserId = args?.advertiserId || "{advertiserId}";
+    const queryGoal = args?.queryGoal || "campaign performance";
+    return `# Custom Query Building Workflow
+
+## Goal: ${queryGoal}
+
+Follow these steps to build a custom Bid Manager query using the \`dbm_run_custom_query\` tool.
+
+---
+
+## Step 1: Determine Report Type
+
+**Most common:** \`STANDARD\` for general delivery metrics.
+
+Available types:
+- \`STANDARD\` - Impressions, clicks, cost, conversions (most common)
+- \`FLOODLIGHT\` - Conversion tracking with Floodlight data
+- \`YOUTUBE\` - TrueView/YouTube-specific metrics
+- \`REACH\` - Reach and frequency metrics
+
+Fetch \`report-types://all\` for full details.
+
+---
+
+## Step 2: Choose Dimensions (groupBys)
+
+Dimensions determine how results are broken down.
+
+**Common groupBys for ${queryGoal}:**
+- \`FILTER_DATE\` - Daily breakdown
+- \`FILTER_MEDIA_PLAN\` - By campaign
+- \`FILTER_LINE_ITEM\` - By line item
+- \`FILTER_DEVICE_TYPE\` - By device
+- \`FILTER_CREATIVE\` - By creative
+
+Fetch \`filter-types://all\` for the complete list of ${278} available filters.
+
+---
+
+## Step 3: Select Metrics
+
+Choose the metrics you want to measure.
+
+**Common metrics for ${queryGoal}:**
+- \`METRIC_IMPRESSIONS\` - Total impressions
+- \`METRIC_CLICKS\` - Total clicks
+- \`METRIC_CTR\` - Click-through rate
+- \`METRIC_TOTAL_MEDIA_COST_ADVERTISER\` - Total spend
+- \`METRIC_TOTAL_CONVERSIONS\` - Total conversions
+
+Fetch \`metric-types://all\` for the complete list of ${100} available metrics.
+
+---
+
+## Step 4: Set Filters
+
+Filters restrict the data to specific values.
+
+**Required filter:**
+\`\`\`json
+{ "type": "FILTER_ADVERTISER", "value": "${advertiserId}" }
+\`\`\`
+
+**Optional filters:**
+- \`FILTER_MEDIA_PLAN\` - Specific campaign(s)
+- \`FILTER_LINE_ITEM\` - Specific line item(s)
+- \`FILTER_DATE\` - Specific date range
+
+---
+
+## Step 5: Set Date Range
+
+**Presets (recommended):**
+- \`LAST_7_DAYS\` - Quick recent view
+- \`LAST_30_DAYS\` - Monthly view
+- \`MONTH_TO_DATE\` - Current month
+- \`PREVIOUS_MONTH\` - Last complete month
+
+**Custom dates:**
+\`\`\`json
+{
+  "startDate": "2025-01-01",
+  "endDate": "2025-01-31"
+}
+\`\`\`
+
+---
+
+## Step 6: Execute Query
+
+Example query for ${queryGoal}:
+
+\`\`\`json
+{
+  "reportType": "STANDARD",
+  "groupBys": ["FILTER_DATE", "FILTER_MEDIA_PLAN"],
+  "metrics": [
+    "METRIC_IMPRESSIONS",
+    "METRIC_CLICKS",
+    "METRIC_CTR",
+    "METRIC_TOTAL_MEDIA_COST_ADVERTISER"
+  ],
+  "filters": [
+    { "type": "FILTER_ADVERTISER", "value": "${advertiserId}" }
+  ],
+  "dateRange": {
+    "preset": "LAST_7_DAYS"
+  }
+}
+\`\`\`
+
+---
+
+## Validation Options
+
+- \`strictValidation: true\` (default) - Validates all filter/metric names against known values
+- \`strictValidation: false\` - Passes unknown values to API (useful for new API features)
+
+---
+
+## Output Options
+
+- \`outputFormat: "structured"\` (default) - Returns JSON array of records
+- \`outputFormat: "csv"\` - Returns raw CSV string
+
+---
+
+## Common Errors
+
+| Error | Solution |
+|-------|----------|
+| "Unknown filter type" | Check spelling, fetch \`filter-types://all\` |
+| "Unknown metric type" | Check spelling, fetch \`metric-types://all\` |
+| "Report failed" | Check date range validity, reduce groupBys |
+| "No data returned" | Verify advertiser ID, check filters aren't too restrictive |
+
+---
+
+## Next Steps
+
+1. Run the query with \`dbm_run_custom_query\`
+2. Analyze results
+3. Refine groupBys/metrics based on findings
+4. Use \`dbm_get_historical_metrics\` for trend analysis
+`;
+}
+//# sourceMappingURL=custom-query-workflow.prompt.js.map

package/dist/mcp-server/prompts/definitions/custom-query-workflow.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"custom-query-workflow.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/custom-query-workflow.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,yBAAyB,GAAW;IAC/C,IAAI,EAAE,uBAAuB;IAC7B,WAAW,EACT,+FAA+F;IACjG,SAAS,EAAE;QACT;YACE,IAAI,EAAE,cAAc;YACpB,WAAW,EAAE,8BAA8B;YAC3C,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EACT,8FAA8F;YAChG,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,6BAA6B,CAAC,IAA6B;IACzE,MAAM,YAAY,GAAG,IAAI,EAAE,YAAY,IAAI,gBAAgB,CAAC;IAC5D,MAAM,SAAS,GAAG,IAAI,EAAE,SAAS,IAAI,sBAAsB,CAAC;IAE5D,OAAO;;WAEE,SAAS;;;;;;;;;;;;;;;;;;;;;;;;wBAwBI,SAAS;;;;;;;wDAOuB,GAAG;;;;;;;;uBAQpC,SAAS;;;;;;;wDAOwB,GAAG;;;;;;;;;;2CAUhB,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oBA8BnC,SAAS;;;;;;;;;;;;;+CAakB,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyC1D,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "./types.js";
+export declare const pacingPerformanceAnalysisPrompt: Prompt;
+export declare function getPacingPerformanceAnalysisMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=pacing-performance-analysis.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"pacing-performance-analysis.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAQzC,eAAO,MAAM,+BAA+B,EAAE,MAqB7C,CAAC;AAEF,wBAAgB,mCAAmC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAsLzF"}

package/dist/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.js

@@ -0,0 +1,204 @@
+export const pacingPerformanceAnalysisPrompt = {
+    name: "pacing_performance_analysis_workflow",
+    description: "Step-by-step guide for DV360 pacing assessment and performance deep-dive: check delivery pacing, analyze CPM/CTR/CPA/ROAS, identify historical trends, and recommend bid/budget adjustments via dv360-mcp.",
+    arguments: [
+        {
+            name: "campaignId",
+            description: "DV360 Campaign ID to analyze",
+            required: true,
+        },
+        {
+            name: "advertiserId",
+            description: "DV360 Advertiser ID",
+            required: true,
+        },
+        {
+            name: "focus",
+            description: "Analysis focus: 'pacing', 'performance', or 'both' (default: both)",
+            required: false,
+        },
+    ],
+};
+export function getPacingPerformanceAnalysisMessage(args) {
+    const campaignId = args?.campaignId || "{campaignId}";
+    const advertiserId = args?.advertiserId || "{advertiserId}";
+    const focus = args?.focus || "both";
+    return `# DV360 Pacing & Performance Analysis
+
+Campaign: \`${campaignId}\`
+Advertiser: \`${advertiserId}\`
+Focus: \`${focus}\`
+
+---
+
+## Step 1: Assess Delivery Pacing
+
+Check whether the campaign is on track to spend its budget by flight end.
+
+\`\`\`json
+{
+  "tool": "dbm_get_pacing_status",
+  "params": {
+    "campaignId": "${campaignId}",
+    "advertiserId": "${advertiserId}"
+  }
+}
+\`\`\`
+
+**Interpret the pacing percentage:**
+
+| Pacing % | Status | Action |
+|----------|--------|--------|
+| 95–105% | On pace | No action needed |
+| 85–94% | Slightly under | Monitor — may self-correct |
+| 70–84% | Underdelivering | Investigate and adjust bids/targeting |
+| < 70% | Severely under | Urgent — likely a configuration or targeting issue |
+| 106–115% | Slightly over | Monitor — consider lowering bids |
+| > 115% | Overspending | Reduce bids or pause line items immediately |
+
+---
+
+## Step 2: Analyze Performance Metrics
+
+Get calculated performance metrics for the campaign:
+
+\`\`\`json
+{
+  "tool": "dbm_get_performance_metrics",
+  "params": {
+    "campaignId": "${campaignId}",
+    "advertiserId": "${advertiserId}",
+    "dateRange": "LAST_7_DAYS"
+  }
+}
+\`\`\`
+
+**Key metrics to evaluate:**
+
+| Metric | What It Tells You | Action Threshold |
+|--------|-------------------|------------------|
+| **CPM** | Cost efficiency of impressions | Compare to vertical benchmarks |
+| **CTR** | Ad engagement rate | < 0.05% suggests creative fatigue or poor targeting |
+| **CPA** | Cost per acquisition | Compare to target CPA goal |
+| **ROAS** | Return on ad spend | < 1.0 means losing money |
+
+---
+
+## Step 3: Identify Historical Trends
+
+Pull time-series data to spot trends over time:
+
+\`\`\`json
+{
+  "tool": "dbm_get_historical_metrics",
+  "params": {
+    "campaignId": "${campaignId}",
+    "advertiserId": "${advertiserId}",
+    "startDate": "{YYYY-MM-DD}",
+    "endDate": "{YYYY-MM-DD}",
+    "granularity": "DAILY"
+  }
+}
+\`\`\`
+
+**What to look for:**
+
+- **CPM trending up** → Competition increasing or targeting too narrow. Consider broadening audience.
+- **CTR trending down** → Creative fatigue. Recommend creative refresh.
+- **Spend dropping day-over-day** → Delivery issue. Check targeting restrictions, bid floors, budget caps.
+- **CPA spiking** → Conversion drop-off. Check landing page, conversion tracking, audience quality.
+- **Consistent flat delivery** → May indicate a frequency cap or pacing issue.
+
+---
+
+## Step 4: Build a Custom Deep-Dive Query (Optional)
+
+For more granular analysis, compose a custom Bid Manager query:
+
+\`\`\`json
+{
+  "tool": "dbm_run_custom_query",
+  "params": {
+    "reportType": "STANDARD",
+    "timeRange": "LAST_14_DAYS",
+    "metrics": [
+      "METRIC_IMPRESSIONS",
+      "METRIC_CLICKS",
+      "METRIC_TOTAL_MEDIA_COST_ADVERTISER",
+      "METRIC_TOTAL_CONVERSIONS",
+      "METRIC_REVENUE_ADVERTISER"
+    ],
+    "dimensions": [
+      "FILTER_LINE_ITEM"
+    ],
+    "filters": [
+      {
+        "type": "FILTER_ADVERTISER",
+        "value": "${advertiserId}"
+      },
+      {
+        "type": "FILTER_CAMPAIGN",
+        "value": "${campaignId}"
+      }
+    ]
+  }
+}
+\`\`\`
+
+**Resource reference:** Fetch \`metric-types://all\` and \`filter-types://all\` for available metrics and dimensions. Check \`compatibility-rules://all\` to ensure your metric/dimension combination is valid.
+
+---
+
+## Step 5: Diagnose and Recommend
+
+Based on findings from Steps 1–4, determine the root cause and recommended action:
+
+### Underdelivery Diagnosis
+
+| Symptom | Likely Cause | Recommended Action |
+|---------|-------------|-------------------|
+| Low pacing + high CPM | Bid too low for competition | Increase bids via **dv360-mcp** \`dv360_adjust_line_item_bids\` |
+| Low pacing + low CPM | Targeting too narrow | Broaden audience or geo targeting via **dv360-mcp** targeting tools |
+| Low pacing + normal CPM | Budget cap or frequency cap | Check IO/LI budget and frequency settings via **dv360-mcp** \`dv360_get_entity\` |
+| Declining CTR + stable impressions | Creative fatigue | Recommend creative refresh (new creatives via **dv360-mcp**) |
+| High CPA + good CTR | Landing page or conversion issue | Check conversion tracking setup (outside MCP scope) |
+
+### Overspend Diagnosis
+
+| Symptom | Likely Cause | Recommended Action |
+|---------|-------------|-------------------|
+| High pacing + low CPM | Bids too aggressive | Lower bids via **dv360-mcp** \`dv360_adjust_line_item_bids\` |
+| High pacing + high CPM | Budget pacing too aggressive | Adjust pacing to EVEN via **dv360-mcp** \`dv360_update_entity\` |
+
+---
+
+## Step 6: Apply Remediation (via dv360-mcp)
+
+This reporting server (dbm-mcp) is read-only. To make changes, use **dv360-mcp** tools:
+
+- **Adjust bids**: \`dv360_adjust_line_item_bids\` (batch bid changes)
+- **Pause line items**: \`dv360_bulk_update_status\` (pause underperformers)
+- **Update budgets**: \`dv360_update_entity\` with updateMask on budget fields
+- **Modify targeting**: \`dv360_create_assigned_targeting\` / \`dv360_delete_assigned_targeting\`
+
+After making changes, wait at least 2-4 hours for delivery to adjust, then re-run Steps 1-2 to verify improvement.
+
+---
+
+## Summary Template
+
+Present findings in this format:
+
+| Metric | Current Value | Trend (7d) | Status |
+|--------|--------------|------------|--------|
+| Pacing | {X}% | {direction} | {On track / Under / Over} |
+| CPM | \${X.XX} | {direction} | {Normal / High / Low} |
+| CTR | {X.XX}% | {direction} | {Normal / Low} |
+| CPA | \${X.XX} | {direction} | {Below / Above target} |
+| ROAS | {X.XX}x | {direction} | {Profitable / Unprofitable} |
+
+**Diagnosis:** {one-sentence summary}
+**Recommended Actions:** {numbered list of specific actions with tool calls}
+`;
+}
+//# sourceMappingURL=pacing-performance-analysis.prompt.js.map

package/dist/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"pacing-performance-analysis.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/pacing-performance-analysis.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,+BAA+B,GAAW;IACrD,IAAI,EAAE,sCAAsC;IAC5C,WAAW,EACT,4MAA4M;IAC9M,SAAS,EAAE;QACT;YACE,IAAI,EAAE,YAAY;YAClB,WAAW,EAAE,8BAA8B;YAC3C,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,cAAc;YACpB,WAAW,EAAE,qBAAqB;YAClC,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,OAAO;YACb,WAAW,EAAE,oEAAoE;YACjF,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,mCAAmC,CAAC,IAA6B;IAC/E,MAAM,UAAU,GAAG,IAAI,EAAE,UAAU,IAAI,cAAc,CAAC;IACtD,MAAM,YAAY,GAAG,IAAI,EAAE,YAAY,IAAI,gBAAgB,CAAC;IAC5D,MAAM,KAAK,GAAG,IAAI,EAAE,KAAK,IAAI,MAAM,CAAC;IAEpC,OAAO;;cAEK,UAAU;gBACR,YAAY;WACjB,KAAK;;;;;;;;;;;;qBAYK,UAAU;uBACR,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;;qBA0Bd,UAAU;uBACR,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;qBAyBd,UAAU;uBACR,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oBAyCf,YAAY;;;;oBAIZ,UAAU;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6D7B,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/tool-schema-exploration.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "./types.js";
+export declare const toolSchemaExplorationPrompt: Prompt;
+export declare function getToolSchemaExplorationMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=tool-schema-exploration.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/tool-schema-exploration.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool-schema-exploration.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/tool-schema-exploration.prompt.ts"],"names":[],"mappings":"AASA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAEzC,eAAO,MAAM,2BAA2B,EAAE,MAiBzC,CAAC;AAEF,wBAAgB,+BAA+B,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAiDrF"}

package/dist/mcp-server/prompts/definitions/tool-schema-exploration.prompt.js

@@ -0,0 +1,66 @@
+export const toolSchemaExplorationPrompt = {
+    name: "tool_schema_exploration_workflow",
+    description: "Step-by-step workflow for exploring available MCP tools, prompts, and resources with minimal context usage.",
+    arguments: [
+        {
+            name: "serverFocus",
+            description: "Server to focus on: dbm-mcp, dv360-mcp, or both (default: both)",
+            required: false,
+        },
+        {
+            name: "objective",
+            description: "Exploration objective (e.g. query planning, entity schema lookup, troubleshooting)",
+            required: false,
+        },
+    ],
+};
+export function getToolSchemaExplorationMessage(args) {
+    const serverFocus = args?.serverFocus || "both";
+    const objective = args?.objective || "tool and schema discovery";
+    return `# Tool and Schema Exploration Workflow
+
+## Context
+- Focus: ${serverFocus}
+- Objective: ${objective}
+
+Use this workflow to discover capabilities while minimizing token/context bloat.
+
+## Step 1: List capabilities first
+1. Call \`tools/list\`
+2. Call \`prompts/list\`
+3. Call \`resources/list\`
+
+Do not fetch large resources before narrowing scope.
+
+## Step 2: Narrow to one task path
+Pick one immediate action:
+- Build a custom reporting query
+- Inspect DV360 entity schema/update fields
+- Troubleshoot delivery/performance
+
+## Step 3: Fetch only targeted resources
+Prefer smallest resources first:
+- For filters: \`filter-types://category/{slug}\`
+- For metrics: \`metric-types://category/{slug}\`
+- Use \`://all\` resources only when needed
+- For DV360 entities: \`entity-schema://{entityType}\`, \`entity-fields://{entityType}\`, \`entity-examples://{entityType}\`
+
+## Step 4: Validate compatibility before execution
+- Confirm reportType/filter/metric compatibility via \`compatibility-rules://all\`
+- Confirm DV360 updateMask fields via \`entity-fields://{entityType}\`
+
+## Step 5: Execute one smallest-viable tool call
+Start with one call, inspect output, then iterate.
+
+## Context-minimization rules
+- Keep text summaries concise; rely on structured output where available
+- Avoid copying full JSON into chat unless requested
+- Reuse fetched resource facts instead of re-fetching full docs
+
+## Suggested next prompt
+- For reporting query construction: \`custom_query_workflow\`
+- For reporting troubleshooting: \`troubleshoot_report\`
+- For DV360 budget/campaign setup: use corresponding dv360-mcp prompts
+`;
+}
+//# sourceMappingURL=tool-schema-exploration.prompt.js.map

package/dist/mcp-server/prompts/definitions/tool-schema-exploration.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool-schema-exploration.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/tool-schema-exploration.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,2BAA2B,GAAW;IACjD,IAAI,EAAE,kCAAkC;IACxC,WAAW,EACT,6GAA6G;IAC/G,SAAS,EAAE;QACT;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,iEAAiE;YAC9E,QAAQ,EAAE,KAAK;SAChB;QACD;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EACT,oFAAoF;YACtF,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,MAAM,UAAU,+BAA+B,CAAC,IAA6B;IAC3E,MAAM,WAAW,GAAG,IAAI,EAAE,WAAW,IAAI,MAAM,CAAC;IAChD,MAAM,SAAS,GAAG,IAAI,EAAE,SAAS,IAAI,2BAA2B,CAAC;IAEjE,OAAO;;;WAGE,WAAW;eACP,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCvB,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/troubleshoot-report.prompt.d.ts

@@ -0,0 +1,4 @@
+import type { Prompt } from "./types.js";
+export declare const troubleshootReportPrompt: Prompt;
+export declare function getTroubleshootReportMessage(args?: Record<string, string>): string;
+//# sourceMappingURL=troubleshoot-report.prompt.d.ts.map

package/dist/mcp-server/prompts/definitions/troubleshoot-report.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"troubleshoot-report.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/troubleshoot-report.prompt.ts"],"names":[],"mappings":"AASA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAEzC,eAAO,MAAM,wBAAwB,EAAE,MAgBtC,CAAC;AAEF,wBAAgB,4BAA4B,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAkKlF"}