MCP App Store
by KeenEthics
Intentwise icon

Intentwise MCP Server for ChatGPT

By Intentwise

Overview

Intentwise AI Gateway is the intelligence layer between your commerce data and your AI assistant. Built on the Intentwise Commerce Observability Platform, it unifies advertising, retail, inventory, and competitive signals across Amazon, Walmart, Criteo, Meta, TikTok, Google, and other marketplaces into one connected, AI-ready foundation — the ground truth for both people and AI agents to act on Ask deep business questions in plain English and get accurate, domain-specific answers. A structured semantic layer, enriched with your own taxonomies and brand context, interprets commerce signals correctly and reduces hallucinations, so responses reflect the real structure and language of your business. No SQL, no waiting on dashboards. Diagnose what's driving performance, compare periods, spot trends, break results down by campaign, product, or marketplace, and build custom reports on demand. AI Gateway also turns visibility into controlled execution — discovering audiences and targets and building campaigns, always with your confirmation before anything changes. As the platform grows, the Gateway continues to expand across intelligence, automation, and agent-driven workflows. Read capabilities retrieve and analyze your data; write capabilities act only after you approve.

How to connect

  1. ChatGPT: Open the Intentwise listing in the ChatGPT app directory and choose Connect. ChatGPT listing Intentwise exposes 15 tools here.

Tools

create_ad_association

ChatGPT
Creates one or more Amazon ad associations in a single batch call. An ad association links an ad (creative) to an ad group (line item). This tool supports BULK creation — pass multiple associations in the dsp_ad_associations array to create them all in one request instead of calling the tool repeatedly. CHANNEL: Only 'AMAZON_DSP' is supported; set channel to 'AMAZON_DSP' and populate 'dsp_ad_associations'. PREREQUISITE — organization_id, account_id, adGroupId, adId, and channel are required: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts to discover available accounts and their account_id. 3. Deduce the channel from the user's request. 4. The adGroupId must reference an existing ad group (line item). Use create_ad_group first if needed. 5. The adId must reference an existing ad (creative). Obtain by calling query_structure_data_by_entity_type. IMPORTANT: Before calling this tool, present a single CONSOLIDATED plan summary covering ALL ad associations (ad group, ad/creative, etc. for each) in one view. Receive explicit user approval on the full plan before proceeding. Never call this tool without prior user confirmation. RESPONSE HANDLING — On success, the tool returns JSON with a message field. Relay message to the user.

create_ad_group

ChatGPT
Creates one or more Amazon ad groups (called 'line items' in DSP) in a single batch call. This tool supports BULK creation — pass multiple ad groups in the dsp_ad_groups array to create them all in one request instead of calling the tool repeatedly. NOT SUPPORTED: Tactic ad groups (targetingSettings.automatedTargetingTactic). This tool only creates standard DSP line items. Do NOT set automatedTargetingTactic — all tactic types are out of scope (e.g. CUSTOMER_ACQUISITION, REMARKETING, RETENTION, MAXIMIZE_PERFORMANCE, PROSPECTING, AWARENESS, SEARCH). CHANNEL: Only 'AMAZON_DSP' is supported; set channel to 'AMAZON_DSP' and populate 'dsp_ad_groups'. PREREQUISITE — organization_id, account_id, campaign_id, and channel are required: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts to discover available accounts and their account_id. 3. Deduce the channel from the user's request. 4. The campaignId must reference an existing campaign (order). Use create_campaign first if needed. 5. Call discover_advertised_product_category to get advertisedProductCategoryIds. 6. Every standard ad group requires a LIFETIME budget — ask the user for the amount before calling this tool. 7. Every standard ad group requires bid.baseBid — ask the user for the bid amount before calling this tool. IMPORTANT: Before calling this tool, present a single CONSOLIDATED plan summary covering ALL ad groups in one view. Receive explicit user approval on the full plan before proceeding. Never call this tool without prior user confirmation. RESPONSE HANDLING — On success, the tool returns JSON with a message field. Relay message to the user. Related tools that operate on the result: create_target (add targeting criteria) and create_ad_association (link ads/creatives).

create_campaign

ChatGPT
Creates one or more Amazon DSP campaigns (called 'orders' in DSP) in a single batch call. This tool supports BULK creation — pass multiple campaigns in the dsp_campaigns array to create them all in one request instead of calling the tool repeatedly. CHANNEL: Only 'AMAZON_DSP' is supported; set channel to 'AMAZON_DSP' and populate 'dsp_campaigns'. PREREQUISITE — organization_id, account_id, and channel are required: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts to discover available accounts and their account_id. 3. Use channel 'AMAZON_DSP'. LIMITATION: After creating a campaign, only STANDARD ad groups are supported via create_ad_group. Tactic ad groups (targetingSettings.automatedTargetingTactic) are NOT supported — all tactic types are out of scope. Do not attempt ad groups with automatedTargetingTactic set. IMPORTANT: Before calling this tool, present a single CONSOLIDATED plan summary covering ALL campaigns in one view. Receive explicit user approval on the full plan before proceeding. Never call this tool without prior user confirmation. RESPONSE HANDLING — On success, the tool returns JSON with a message field. Relay message to the user. Related tools that operate on the result: create_ad_group (add standard ad groups).

create_target

ChatGPT
Creates one or more Amazon targeting criteria in a single batch call. This tool supports BULK creation — pass multiple targets in the dsp_targets array to create them all in one request instead of calling the tool repeatedly. CHANNEL: Only 'AMAZON_DSP' is supported; set channel to 'AMAZON_DSP' and populate 'dsp_targets'. PREREQUISITE — organization_id, account_id, and channel are required: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts to discover available accounts and their account_id. 3. Deduce the channel from the user's request. 4. Call the appropriate discovery tool for the target type (discover_static_targets, target_discovery_by_type_and_query, or target_discovery_by_audience) and use the returned values in targetDetails. 5. Each target must specify targetType and the corresponding targetDetails object. 6. Set adGroupId for ad-group level targets or campaignId for campaign-level targets. NEGATIVE TARGETING: - Include-only (no exclusions): for targetType KEYWORD, DEVICE, CONTENT_CATEGORY (contentCategoryTarget / IAB-style categories), or DOMAIN — the API only supports inclusion. Do not ask the user about negative/exclude; always set negative to false. - For all other target types: explicitly ask whether each target should be negative (excluded) or positive (included) before setting negative. AUDIENCE TARGETING (targetType AUDIENCE): - Up to 500 audience targets can be associated per ad group. - groupId is required on every audience target. Use '1'–'10' for inclusion groups; '11' for the exclusion group. - Include vs exclude is controlled by the negative field: negative=false (include), negative=true (exclude). - Audiences to include together (OR) → same groupId from '1'–'10' + negative=false. - Audiences to exclude together (AND) → groupId '11' + negative=true. - Every audience in a groupId must have the same negative value. - Use a new groupId from '1'–'10' for a separate inclusion OR-set. - Do NOT set inGroupOperator, acrossGroupOperator, intraOperator, or interOperator — boolean logic is applied automatically by Amazon: • Within an inclusion group (negative=false): audiences joined by OR/ANY. • Within the exclusion group (negative=true): audiences joined by AND/ALL. • Across groups: groups are joined by AND logic. IMPORTANT: Before calling this tool, present a single CONSOLIDATED plan summary covering ALL targets in one view. Receive explicit user approval on the full plan before proceeding. Never call this tool without prior user confirmation. RESPONSE HANDLING — On success, the tool returns JSON with a message field. Relay message to the user. Related tools that operate on the result: create_ad_association (link ads/creatives).

discover_advertised_product_category

ChatGPT
Returns the list of Amazon DSP advertised product categories available for an account. These are the product categories an advertiser can target based on their catalog.

discover_static_targets

ChatGPT
Returns Amazon DSP static target lists that don't require search queries. INVENTORY_SOURCE returns available deals and inventory sources; CONTENT_CATEGORY returns standard IAB content categories.

dsp_create_conversion_tracking_products

ChatGPT
Adds one or more products to conversion tracking for a DSP campaign. Products are appended to the campaign's existing tracking list. CHANNEL: Only 'AMAZON_DSP' is supported; set channel to 'AMAZON_DSP'. PREREQUISITE — organization_id, account_id, campaign_id, and channel are required: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts to discover available accounts and their account_id. 3. The campaign_id must reference an existing DSP campaign (from create_campaign). PRODUCT ASSOCIATION — For each product, set productAssociation appropriately: - FEATURED: ASIN promoted in campaign creatives. - FEATURED_WITH_VARIATION: featured ASIN with variation tracking. - NOT_FEATURED: additional ASINs to track beyond featured/parent ASINs. Tracking non-featured ASINs prevents conversion data loss after the campaign starts. IMPORTANT: Before calling this tool, present a consolidated plan listing all ASINs, domains, and association types. Receive explicit user approval before proceeding. RESPONSE HANDLING — The tool returns JSON from the agent API: - On full success: a message field summarizing what was added. Present message to the user. - On per-product failure or partial success: errors (array), success (array), and requestId. Each item in errors has index (position in product_tracking_list) and subErrors (each with errorCode, errorMessage, and optional errorId). Present each subErrors[].errorMessage to the user, map index to the ASIN that failed, and include requestId when reporting issues. If success is non-empty, report which products were added and which failed. - On validation gaps: needs_clarification with question and missing fields. - On gateway/auth failures: error, status, and message (generic; no agent detail).

get_amc_insights

ChatGPT
Run an Amazon Marketing Cloud (AMC) analytics query from a natural-language question and return structured report results. WHEN TO USE THIS TOOL — use ONLY when BOTH conditions are true: 1. The account's type field from get_intentwise_accounts is AMAZON_MARKETING_CLOUD. Regular Amazon Seller/Vendor/Ads/DSP accounts do NOT have AMC data — use get_insights for those. 2. The user's question is about an AMC report. AMC is Amazon's privacy-safe clean room — it provides anonymized, event-level signals across Sponsored Ads and DSP to produce cross-channel insights (path-to-conversion, exposure group analysis, frequency distribution, geographic reach, NTB analysis across all ad product types) that standard per-format ad reporting cannot. Supported reports: - Sponsored Ads vs DSP overlap (reach, unique reach, NTB metrics, ROAS by exposure group) - New-to-brand gateway ASINs (which promoted ASINs attract the most NTB customers) - ASIN purchase overlap / upsell (which ASINs are bought together, product affinity, cross-sell) - DSP campaign performance by geography (reach, purchases, ROAS broken out by country, state, or DMA — geographic DSP breakdown does NOT exist in standard DSP reporting; always use this tool for geo questions) - DSP reach and impression frequency (unique users reached and frequency distribution by bucket: how many users saw 1×, 2–3×, 4–6×, 7+× impressions — standard DSP has total impressions only, NOT per-bucket distribution; always use this tool for frequency distribution questions) - Path-to-conversion / customer journey analysis (which ad touchpoint sequences led to purchase, most efficient paths, NTB journeys) - Path-to-conversion with Brand Store / BSI touchpoints (paid dataset; brand-store-influenced journeys) - Customer audience / shopper funnel (impressions → clicks → conversions by NEW TO BRAND vs REPEAT; CAC) - Organic vs ad-exposed purchases by ASIN (non-ad-exposed vs ad-exposed shoppers, sales, NTB, Subscribe & Save) - New-to-brand customer impact (NTB rate, NTB sales by ad product type or campaign) - Ad-attributed branded searches (which DSP campaigns drive branded keyword searches on Amazon) - Time-to-conversion (how long after seeing an ad customers make a purchase — time bucket distribution) - Tentpole phase overlap (ad strategy performance across Lead Up, Event Day, and Lead Out phases for peak events like Prime Day and Black Friday) - Shopper insight abandonment events (ASIN-level cart abandonment, detail page view drop-off, purchase funnel analysis, and NTB buyers per product) - Custom first-touch attribution (28-day window; 100% credit to first touchpoint — which channels/campaigns attract customers) - Custom last-touch attribution (28-day window; 100% credit to last touchpoint — which channels/campaigns convert customers) - Custom linear-touch attribution (28-day window; equal credit across all touchpoints — full-path contribution; may include fractional conversions) - Brand lifetime revenue from Amazon Retail Purchases / ARP (NTB cohort 3/6/12-month LTR by brand and purchase month; revenue-only, no ad cost) - Purchase frequency from ARP (how many users bought 1x vs 2x vs 3x+ for a brand) - Days between purchases from ARP (repurchase cadence / day-gap distribution by brand) - ASIN-level (entry product) lifetime revenue from ARP (product vs customer LTR for NTB entry ASINs) - Brand Store page performance (sessions, visits, dwell time, and purchase conversions attributed to the last Brand Store page viewed before purchase — use for which pages drive the most engagement or NTB purchases) Do NOT use this tool for standard campaign/keyword/bid performance, Seller Central, or Vendor Central questions — use get_insights for those. PREREQUISITE SEQUENCE: 1. Call get_organization to obtain your organization_id. 2. Call get_intentwise_accounts(organization_id=..., account_type_filter='AMAZON_MARKETING_CLOUD') to find AMC accounts. Only accounts with type=AMAZON_MARKETING_CLOUD can be queried with this tool. If no accounts are returned, the organization has no AMC integration set up. 3. C…

get_insights

ChatGPT
Generate and execute a BigQuery SQL query from a natural-language request for a SINGLE account per call. Channels (REQUIRED — pick one): 'amazon' (data sources: ads, seller_central, vendor_central, dsp, share_of_voice, content), 'walmart' (data_source 'ads', or 'seller'/'vendor' marketplace), 'criteo' (retail-media 'ads' across retailers — Target/Roundel, Dick's Sporting Goods, Golf Galaxy, Lowe's, Best Buy, Costco — filter by retailer_name), 'instacart' ('ads', mcp_instacart_data), 'tiktok' ('ads' for Ads or 'tiktok_shop' for TikTok Shop, mcp_tiktok_data), 'meta' ('ads', mcp_meta_data), and 'google' (Google Ads 'ads', mcp_google_data). DISAMBIGUATION: 'channel' is the PLATFORM; data_source (ads, dsp, seller_central, vendor_central, share_of_voice, content, tiktok_shop, Walmart seller/vendor) is a SEPARATE choice WITHIN a channel — never present a data_source like 'Amazon DSP' or 'Amazon Seller Central' as a platform option. If the account has more than one ads channel (e.g. both Amazon and Criteo, or Amazon and Walmart) and the user's request does not make the platform clear, ask which platform before calling this tool — do NOT guess, and do NOT list data_sources as the choices. Only SELECT queries on intentwise_ecommerce_graph tables are supported. INSERT, UPDATE, DELETE, MERGE and other write operations are not supported. PREREQUISITE — organization_id, account_id, channel, and data_source are all required. When the account has more than one ads channel and the right one is unclear, ask the user rather than guessing. Follow this sequence: 1. Call get_organization to discover your organization_id. 2. Call get_intentwise_accounts(organization_id=...) to discover available accounts. Each account includes available_data_sources — a list of { data_source_type, channel } pairs representing the active integrations for that account. IMPORTANT: before calling this tool, verify that the channel and data_source you intend to pass exist as a matching pair in the account's available_data_sources. If the combination is not present, do NOT call this tool — the data source is not enabled for that account. Accounts with an empty available_data_sources list have no active integrations and cannot be queried. 3. Call search_schema at least once per session with the user's query text to discover the available tables and their descriptions. For DSP queries (orders, line items, order goal, awareness/consideration/conversion), pass channel=amazon and data_source=dsp so results are from the DSP schema; otherwise you may get Sponsored Ads (ecommerce) tables. The schema contains similarly-named tables that serve different purposes (e.g., product_summary = holistic product data with organic metrics; advertised_product_summary = ad-level product data by campaign/adgroup — no organic metrics; product_summary = pre-joined flat table at ASIN x day grain with ads, SC/VC sales, SC traffic (sessions, page views, buy box), and VC glance views — use for any product-level cross-metric analysis instead of joining multiple product reports). The search results include table descriptions that explain when to use each table. After reviewing search results, fetch the relevant table resource via resources/read using the resource_id from search results (e.g. schema://intentwise-ecommerce-graph/v1/table/<table_name> for ads, schema://intentwise-dsp/v1/table/<table_name> for DSP, schema://intentwise-seller-central/v1/table/<table_name> for Seller Central, schema://intentwise-vendor-central/v1/table/<table_name> for Vendor Central) to see columns, semantic_layer, allowed group-by sets, and enum values. Each table resource includes channel, data_source, and in most cases an entity field — read the entity value from the resource and pass it directly to get_insights. Examples: searchterm_summary → entity=search_term; sellercentral_ordersbydate_report → entity=order; dsp_order_report → entity=order; dsp_lineitem_report → entity=lineitem; dsp_creative_report → entity=creative; dsp_audience_report → entity=audience; search_query_performance → entity=search_query; se…

get_intentwise_accounts

ChatGPT
Returns the list of AMS accounts for a given organization. organization_id is required — obtain it from get_organization first. Non-SUPER_ADMIN users must pass their own organization_id. SUPER_ADMIN users may pass any valid organization_id. Supports optional heuristic filtering for account name and account type. Each account includes an available_data_sources list of { data_source_type, channel, description } entries representing the active data source integrations for that account. An empty available_data_sources list means the account has no active data source integrations.

get_organization

ChatGPT
Returns the list of Intentwise organizations the authenticated user has access to. Non-SUPER_ADMIN users will see only their own organization. SUPER_ADMIN users will see all active organizations. Call this first to obtain the organization_id required by get_intentwise_accounts and get_insights.

query_structure_data_by_entity_type

ChatGPT
Query structure/reference metadata for ad entities in an account. Parameters: app_name, organizationId, businessGroupId, accountId, adEntityType, optional nameFilter, optional page, optional size. Supported adEntityType values are CAMPAIGN, AD_GROUP, CREATIVE; When app_name is dsp: For dsp Order/Campaign adEntityType value is CAMPAIGN and for dsp LineItem or line item/AdGroup adEntityType value is AD_GROUP and for dsp Creative adEntityType value is CREATIVE. Optional nameFilter: single entity name to search (exact match). Pagination defaults: page=0, size=25.

search_schema

ChatGPT
Search Intentwise schema (ecommerce graph, DSP, Seller Central, and Vendor Central) for relevant tables, columns, and enums. Returns resource_id values you can fetch via resources/read. Each search hit includes an entity field (when available) that identifies what the table contains — use this entity value when calling get_insights. For full column details, fetch the resource via resources/read. When the user asks about DSP (orders, line items, goals, awareness/consideration/conversion), pass channel=amazon and data_source=dsp so results are from the DSP schema. For Walmart Sponsored Ads pass channel=walmart and data_source=ads. For Sponsored Ads (campaigns, keywords, products), use channel=amazon and data_source=ads. Hourly / intraday ad PERFORMANCE — 'ad clicks/impressions/spend/revenue/orders/ACOS/ROAS by hour', 'dayparting', 'by hour of day' (by keyword / product / target_type / placement / campaign) → channel=amazon, data_source=ads (entity marketing_stream; full hourly ad performance — only search-term text is not here; product × keyword performance is supported — keyword_text and product/ASIN on the same row). Campaign BUDGET PACING — 'are we running out of budget', 'budget usage/consumption/utilization', 'campaigns over/near budget', 'budget used by hour' → channel=amazon, data_source=ads (entity budget_usage; hourly budget, budget_usage_percentage, budget_used — pacing only, no ad spend/revenue). Branded/competitor/generic keyword or search-term split → data_source=ads (is_brand_/is_competitor_ flags on keyword/search_term). Products by a custom attribute (product group, category, unit cost, parent ASIN/brand) → entity=product_attributes (SPARSE per-ASIN ref; NOT the full product list, no metrics; metrics-by-attribute = combine with product/advertised_product). For Seller Central data (inventory, FBA health, orders, returns, storage fees, shipments, settlement/financials), use channel=amazon and data_source=seller_central. For Vendor Central data (purchase orders, retail analytics inventory, forecast, Net PPM, coupons, rapid retail sales), use channel=amazon and data_source=vendor_central. Hourly/intraday ordered units or revenue, 'sales by hour', rapid retail sales → channel=amazon, data_source=vendor_central (entity rapid_retail_sales). For competitive Share of Voice — organic/ad search-RESULT placement share AND organic/ad rank/position vs competitors for tracked keywords (brand / keyword / product), incl. 'organic rank', 'organic position', 'where do I rank for keyword X', 'share of voice', 'ranking presence' — use channel=amazon and data_source=share_of_voice. For product listing / detail-page data (Best Sellers Rank / BSR, sub-category rank, reviews, ratings, listing attributes) use channel=amazon and data_source=content. For CRITEO retail-media advertising (a DIFFERENT channel — campaigns / line items / products / keywords across retailers such as Target/Roundel, Ulta, CVS, Walgreens, Costco), use channel=criteo and data_source=ads. If an account has BOTH amazon ads and criteo ads and the user did not specify the platform, ask the user whether they mean Amazon or Criteo before querying. For TIKTOK Ads (campaigns, ad groups, ads/creatives, campaign-by-gender breakdown, and GMV Max shopping campaigns in mcp_tiktok_data), use channel=tiktok and data_source=ads. For META Ads (accounts, campaigns, ad sets, ads in mcp_meta_data), use channel=meta and data_source=ads. For GOOGLE ADS (Search / Shopping / Display / Performance Max: campaigns, ad groups, ads, keywords, search terms, products, product groups, audiences, placements, conversions, landing pages in mcp_google_data), use channel=google and data_source=ads. Omit data_source to search all schemas. IMPORTANT — call search_schema BEFORE get_insights to resolve the entity and to verify which table(s) contain the columns the user needs. Schema internals are diagnostics; present the final data results. INTERPRETING MULTI-TABLE RESULTS — when hits come from multiple tables, decide: 1. ONE table has ALL needed columns (single entity) → single get_insights call wi…

target_discovery_by_audience

ChatGPT
Discovers Amazon DSP audience segments with optional category and name filtering. Supported audience categories: CUSTOM_BUILT, CONTROL_GROUP_HOLDOUTS, NEGATIVE_TARGETING, CONTEXTUAL, COMBINED_AUDIENCES, IN_MARKET, INTEREST, IN_MARKET_BETA, EXPERIMENTAL, ADVERTISER_AUDIENCES, DEVICE, PERFORMANCE_PLUS, LOOKALIKE, DEMOGRAPHIC, THIRD_PARTY, LIFESTYLE, LIFE_EVENT, IN_MARKET_MULTI_COUNTRY. Use searchQuery to filter by audience name.

target_discovery_by_type_and_query

ChatGPT
Searches Amazon DSP targets by query text given by the user. PRODUCT_CATEGORY: search by category name. LOCATION: search by geo text query (city, state, country, postal code). APP: search by app type and text query. PRODUCT: search by product title or comma-separated ASINs (10-char alphanumeric codes).IMPORTANT: The searchQuery is provided by the user and don't assume search query by yourself always ask

Capabilities

Writes

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/intentwise"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/intentwise)