@cesteral/ttd-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/entity-duplication-workflow.prompt.d.ts

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

package/dist/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-duplication-workflow.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AAQjE,eAAO,MAAM,kCAAkC,EAAE,MAgBhD,CAAC;AAEF,wBAAgB,sCAAsC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAsM5F"}

package/dist/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.js

@@ -0,0 +1,215 @@
+export const ttdEntityDuplicationWorkflowPrompt = {
+    name: "ttd_entity_duplication_workflow",
+    description: "Step-by-step guide for duplicating TTD entities (campaigns, ad groups, ads, creatives) using the get-then-create pattern — covers A/B testing, scaling to new markets, and campaign templating.",
+    arguments: [
+        {
+            name: "entityType",
+            description: "Entity type to duplicate: campaign, adGroup, ad, or creative",
+            required: true,
+        },
+        {
+            name: "entityId",
+            description: "TTD entity ID to duplicate",
+            required: true,
+        },
+    ],
+};
+export function getTtdEntityDuplicationWorkflowMessage(args) {
+    const entityType = args?.entityType || "{entityType}";
+    const entityId = args?.entityId || "{entityId}";
+    return `# TTD Entity Duplication Workflow
+
+Entity Type: \`${entityType}\`
+Entity ID: \`${entityId}\`
+
+---
+
+## Overview
+
+TTD does not have a native duplicate/copy API. To duplicate an entity, use the **get-then-create** pattern:
+
+1. Read the source entity
+2. Strip ID fields and update identifying info (names, dates)
+3. Create the copy under the same parent
+4. Verify and activate when ready
+
+---
+
+## Step 1: Read the Source Entity
+
+\`\`\`
+Tool: ttd_get_entity
+Input: {
+  "entityType": "${entityType}",
+  "entityId": "${entityId}"
+}
+\`\`\`
+
+Save the full response — this is your template.
+
+> Fetch \`entity-schema://${entityType}\` for the fields you must strip before re-creating.
+
+---
+
+## Step 2: Prepare the Copy Payload
+
+Starting from the source entity response, make these modifications:
+
+### Fields to Remove (always)
+- The entity's own ID field (e.g., \`CampaignId\`, \`AdGroupId\`, \`AdId\`, \`CreativeId\`)
+- Any read-only metadata: \`CreatedAt\`, \`LastModified\`, \`Version\`, \`Status\` (if auto-set)
+
+### Fields to Update
+- **Name**: Add suffix to distinguish the copy (e.g., \`"Q1 Campaign - Copy"\`)
+- **Dates**: Update \`StartDate\` and \`EndDate\` if needed
+- **Budget/Bid**: Adjust for the new copy's goals
+- **Parent ID**: Keep the same parent (e.g., same \`CampaignId\` for ad group copies)
+
+### Campaign Copy Example
+
+\`\`\`
+Tool: ttd_create_entity
+Input: {
+  "entityType": "campaign",
+  "data": {
+    "AdvertiserId": "{source AdvertiserId}",
+    "CampaignName": "Q1 2025 Brand - Copy",
+    "Budget": { "Amount": 50000, "CurrencyCode": "USD" },
+    "StartDate": "2025-04-01T00:00:00",
+    "EndDate": "2025-06-30T23:59:59",
+    "PacingMode": "PaceAhead"
+  }
+}
+\`\`\`
+
+### Ad Group Copy Example
+
+\`\`\`
+Tool: ttd_create_entity
+Input: {
+  "entityType": "adGroup",
+  "data": {
+    "AdGroupName": "Prospecting US - Copy",
+    "CampaignId": "{parent CampaignId}",
+    "AdvertiserId": "{source AdvertiserId}",
+    "RTBAttributes": {
+      "BudgetSettings": {
+        "Budget": { "Amount": 10000, "CurrencyCode": "USD" },
+        "DailyBudget": { "Amount": 500, "CurrencyCode": "USD" },
+        "PacingMode": "PaceAhead"
+      },
+      "BaseBidCPM": { "Amount": 5.00, "CurrencyCode": "USD" },
+      "MaxBidCPM": { "Amount": 12.00, "CurrencyCode": "USD" }
+    }
+  }
+}
+\`\`\`
+
+**Save**: Note the returned ID from the response.
+
+---
+
+## Step 3: Customize the Copy
+
+After creation, apply your desired differences:
+
+### Change Targeting (Ad Group)
+
+\`\`\`
+Tool: ttd_update_entity
+Input: {
+  "entityType": "adGroup",
+  "entityId": "{new adGroup ID}",
+  "data": {
+    "AdGroupId": "{new adGroup ID}",
+    "CampaignId": "{parent CampaignId}",
+    "AdvertiserId": "{AdvertiserId}",
+    "AdGroupName": "Prospecting UK - Copy",
+    "RTBAttributes": {
+      "BudgetSettings": "...",
+      "BaseBidCPM": { "Amount": 5.00, "CurrencyCode": "USD" },
+      "GeoSegments": ["GBR"]
+    }
+  }
+}
+\`\`\`
+
+---
+
+## Step 4: Verify the Copy
+
+\`\`\`
+Tool: ttd_get_entity
+Input: {
+  "entityType": "${entityType}",
+  "entityId": "{new entity ID}"
+}
+\`\`\`
+
+---
+
+## Step 5: Activate
+
+\`\`\`
+Tool: ttd_bulk_update_status
+Input: {
+  "entityType": "${entityType}",
+  "entityIds": ["{new entity ID}"],
+  "status": "Running"
+}
+\`\`\`
+
+---
+
+## Common Duplication Patterns
+
+### A/B Testing (Bid Test)
+
+1. Duplicate an ad group
+2. Set a different \`BaseBidCPM\` on the copy
+3. Run both simultaneously
+4. Compare via report: \`ttd_get_report\` segmented by \`AdGroupId\`
+
+### Scaling to New Geos
+
+1. Duplicate a proven campaign or ad group
+2. Update geographic targeting on the copy (GeoSegments or SiteList)
+3. Adjust budget for the new market
+4. Activate
+
+### Seasonal Refresh
+
+1. Duplicate a past campaign
+2. Update \`StartDate\`/\`EndDate\` to new period
+3. Update creatives to seasonal versions
+4. Reset budget if needed
+
+### Bulk Duplication
+
+For creating many copies at once:
+
+\`\`\`
+Tool: ttd_bulk_create_entities
+Input: {
+  "entityType": "${entityType}",
+  "items": [
+    { "AdGroupName": "Copy 1 - East", ... },
+    { "AdGroupName": "Copy 2 - West", ... }
+  ]
+}
+\`\`\`
+
+---
+
+## Success Criteria
+
+- [ ] Source entity read and saved
+- [ ] ID fields stripped from payload
+- [ ] Name updated to distinguish the copy
+- [ ] Copy created and ID saved
+- [ ] Desired changes applied (targeting, budget, creatives)
+- [ ] Copy verified via \`ttd_get_entity\`
+- [ ] Activated via \`ttd_bulk_update_status\` only after review
+`;
+}
+//# sourceMappingURL=entity-duplication-workflow.prompt.js.map

package/dist/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-duplication-workflow.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/entity-duplication-workflow.prompt.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,kCAAkC,GAAW;IACxD,IAAI,EAAE,iCAAiC;IACvC,WAAW,EACT,iMAAiM;IACnM,SAAS,EAAE;QACT;YACE,IAAI,EAAE,YAAY;YAClB,WAAW,EAAE,8DAA8D;YAC3E,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,4BAA4B;YACzC,QAAQ,EAAE,IAAI;SACf;KACF;CACF,CAAC;AAEF,MAAM,UAAU,sCAAsC,CAAC,IAA6B;IAClF,MAAM,UAAU,GAAG,IAAI,EAAE,UAAU,IAAI,cAAc,CAAC;IACtD,MAAM,QAAQ,GAAG,IAAI,EAAE,QAAQ,IAAI,YAAY,CAAC;IAEhD,OAAO;;iBAEQ,UAAU;eACZ,QAAQ;;;;;;;;;;;;;;;;;;;;mBAoBJ,UAAU;iBACZ,QAAQ;;;;;;4BAMG,UAAU;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBA8FnB,UAAU;;;;;;;;;;;;mBAYV,UAAU;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBAsCV,UAAU;;;;;;;;;;;;;;;;;;;CAmB5B,CAAC;AACF,CAAC"}

package/dist/mcp-server/prompts/definitions/entity-update-workflow.prompt.d.ts

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

package/dist/mcp-server/prompts/definitions/entity-update-workflow.prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-update-workflow.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/entity-update-workflow.prompt.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AASjE,eAAO,MAAM,6BAA6B,EAAE,MAiB3C,CAAC;AAEF,wBAAgB,iCAAiC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAiJvF"}

package/dist/mcp-server/prompts/definitions/entity-update-workflow.prompt.js

@@ -0,0 +1,162 @@
+export const ttdEntityUpdateWorkflowPrompt = {
+    name: "ttd_entity_update_workflow",
+    description: "Step-by-step guide for safely updating TTD entities using PUT semantics. Covers safe read-modify-write pattern for campaigns, ad groups, ads, creatives, site lists, and bid lists.",
+    arguments: [
+        {
+            name: "entityType",
+            description: "Entity type to update: advertiser, campaign, adGroup, ad, creative, siteList, deal, conversionTracker, or bidList",
+            required: true,
+        },
+        {
+            name: "entityId",
+            description: "TTD entity ID to update",
+            required: true,
+        },
+    ],
+};
+export function getTtdEntityUpdateWorkflowMessage(args) {
+    const entityType = args?.entityType || "{entityType}";
+    const entityId = args?.entityId || "{entityId}";
+    return `# TTD Entity Update Workflow
+
+Entity Type: \`${entityType}\`
+Entity ID: \`${entityId}\`
+
+---
+
+## ⚠️ Critical: TTD Uses PUT (Not PATCH)
+
+TTD's update API uses **full entity replacement** (HTTP PUT). This means:
+- You MUST read the current entity first
+- You MUST include ALL required fields in your update payload
+- Any fields you omit may be reset to defaults or cause API errors
+- Only send changes — but wrap them in the complete required structure
+
+---
+
+## Step 1: Read Current State
+
+Fetch the entity before modifying it:
+
+\`\`\`
+Tool: ttd_get_entity
+Input: {
+  "entityType": "${entityType}",
+  "entityId": "${entityId}"
+}
+\`\`\`
+
+**Save the response.** You will use it as the base for your update payload.
+
+> Fetch \`entity-schema://${entityType}\` for full field reference and \`entity-examples://${entityType}\` for update patterns.
+
+---
+
+## Step 2: Build Your Update Payload
+
+Start with the full current entity from Step 1, then modify only the fields you want to change.
+
+### Campaign Update (Budget Increase)
+
+\`\`\`
+Tool: ttd_update_entity
+Input: {
+  "entityType": "campaign",
+  "entityId": "${entityId}",
+  "data": {
+    "CampaignId": "${entityId}",
+    "AdvertiserId": "{current AdvertiserId}",
+    "CampaignName": "{current CampaignName}",
+    "Budget": { "Amount": 75000, "CurrencyCode": "USD" },
+    "StartDate": "{current StartDate}",
+    "EndDate": "{current EndDate}",
+    "PacingMode": "{current PacingMode}"
+  }
+}
+\`\`\`
+
+### Ad Group Bid Adjustment
+
+\`\`\`
+Tool: ttd_update_entity
+Input: {
+  "entityType": "adGroup",
+  "entityId": "${entityId}",
+  "data": {
+    "AdGroupId": "${entityId}",
+    "CampaignId": "{current CampaignId}",
+    "AdvertiserId": "{current AdvertiserId}",
+    "AdGroupName": "{current AdGroupName}",
+    "RTBAttributes": {
+      "BudgetSettings": "{current BudgetSettings}",
+      "BaseBidCPM": { "Amount": 7.50, "CurrencyCode": "USD" },
+      "MaxBidCPM": { "Amount": 15.00, "CurrencyCode": "USD" }
+    }
+  }
+}
+\`\`\`
+
+### Bulk Bid Adjustment (Preferred for Multiple Ad Groups)
+
+For multiple ad group bids, use the specialized bid tool — it handles read-modify-write atomically:
+
+\`\`\`
+Tool: ttd_adjust_bids
+Input: {
+  "adjustments": [
+    { "adGroupId": "${entityId}", "bidCPM": 7.50 }
+  ]
+}
+\`\`\`
+
+---
+
+## Step 3: Execute the Update
+
+Call \`ttd_update_entity\` with your full payload. Review the response for any errors.
+
+---
+
+## Step 4: Verify the Change
+
+Confirm the update was applied:
+
+\`\`\`
+Tool: ttd_get_entity
+Input: {
+  "entityType": "${entityType}",
+  "entityId": "${entityId}"
+}
+\`\`\`
+
+Compare the returned values with what you set in Step 2.
+
+---
+
+## Gotchas
+
+- **PUT replaces the entity**: Missing required fields cause API errors. Always start from the current state.
+- **Entity IDs in body**: TTD typically requires the entity ID inside the body (e.g., \`CampaignId\` in the campaign object) in addition to the URL.
+- **Budget is lifetime**: Campaign \`Budget.Amount\` is the total lifetime budget, not daily. Use ad group \`DailyBudget\` for day-level pacing.
+- **Status changes**: To pause/resume entities, prefer \`ttd_bulk_update_status\` over manual status field updates.
+- **Bid adjustments**: For bid changes, prefer \`ttd_adjust_bids\` over manual update — it handles the read-modify-write cycle safely.
+
+---
+
+## Rollback
+
+If the update causes issues, restore the original values using the response you saved in Step 1:
+
+\`\`\`
+Tool: ttd_update_entity
+Input: {
+  "entityType": "${entityType}",
+  "entityId": "${entityId}",
+  "data": "{original entity from Step 1}"
+}
+\`\`\`
+
+Always save the original state before making changes.
+`;
+}
+//# sourceMappingURL=entity-update-workflow.prompt.js.map

package/dist/mcp-server/prompts/definitions/entity-update-workflow.prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-update-workflow.prompt.js","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/entity-update-workflow.prompt.ts"],"names":[],"mappings":"AAYA,MAAM,CAAC,MAAM,6BAA6B,GAAW;IACnD,IAAI,EAAE,4BAA4B;IAClC,WAAW,EACT,qLAAqL;IACvL,SAAS,EAAE;QACT;YACE,IAAI,EAAE,YAAY;YAClB,WAAW,EACT,mHAAmH;YACrH,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,yBAAyB;YACtC,QAAQ,EAAE,IAAI;SACf;KACF;CACF,CAAC;AAEF,MAAM,UAAU,iCAAiC,CAAC,IAA6B;IAC7E,MAAM,UAAU,GAAG,IAAI,EAAE,UAAU,IAAI,cAAc,CAAC;IACtD,MAAM,QAAQ,GAAG,IAAI,EAAE,QAAQ,IAAI,YAAY,CAAC;IAEhD,OAAO;;iBAEQ,UAAU;eACZ,QAAQ;;;;;;;;;;;;;;;;;;;;;mBAqBJ,UAAU;iBACZ,QAAQ;;;;;;4BAMG,UAAU,uDAAuD,UAAU;;;;;;;;;;;;;;iBActF,QAAQ;;qBAEJ,QAAQ;;;;;;;;;;;;;;;;;iBAiBZ,QAAQ;;oBAEL,QAAQ;;;;;;;;;;;;;;;;;;;;;sBAqBN,QAAQ;;;;;;;;;;;;;;;;;;;;mBAoBX,UAAU;iBACZ,QAAQ;;;;;;;;;;;;;;;;;;;;;;;;;mBAyBN,UAAU;iBACZ,QAAQ;;;;;;CAMxB,CAAC;AACF,CAAC"}

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

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

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

@@ -0,0 +1 @@
+{"version":3,"file":"report-generation-workflow.prompt.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/prompts/definitions/report-generation-workflow.prompt.ts"],"names":[],"mappings":"AAQA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,oCAAoC,CAAC;AAEjE,eAAO,MAAM,8BAA8B,EAAE,MAW5C,CAAC;AAEF,wBAAgB,kCAAkC,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,MAAM,CAuJxF"}