ExD Accelerator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORG_ID | Yes | IMS Org ID (e.g., ...@AdobeOrg) | |
| CLIENT_ID | Yes | Adobe Developer Console Client ID | |
| TENANT_ID | Yes | Tenant ID (e.g., acssandboxgdcthree) | |
| SANDBOX_NAME | Yes | Adobe Experience Platform sandbox name | |
| CLIENT_SECRET | Yes | Adobe Developer Console Client Secret | |
| ITEM_CATALOG_ID | Yes | Item catalog ID (e.g., xcore:decision-catalog:...) | |
| DECISIONING_SCHEMA_URI | Yes | Decisioning schema URI (e.g., https://ns.adobe.com/.../schemas/...) | |
| DECISIONING_SCHEMA_ALT_ID | Yes | Decisioning schema alternate ID (e.g., _....schemas....) |
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 |
|---|---|
| parse_csv_and_suggestA | Parse a product/offer CSV, infer XDM types for each column, and suggest schema fields, eligibility rules, and ranking formulas. Always call this first — no data is written. |
| create_offer_metadata_fieldgroupA | Create a new XDM fieldgroup from CSV column names and attach it to the ExD decisioning schema. Will check for an existing fieldgroup with the same name first. Requires confirmed: true to execute — previews first. |
| bulk_create_offersA | Bulk-create ExD offer items from CSV rows. Each row becomes one offer. Requires confirmed: true to execute — previews payloads first. Use dry_run: true to inspect full JSON payloads. |
| create_collectionA | Create an offer item collection with a filter constraint. Requires confirmed: true to execute. |
| create_eligibility_ruleC | Create a PQL eligibility rule for Experience Decisioning. Requires confirmed: true to execute. |
| create_ranking_formulaC | Create a ranking formula for Experience Decisioning. Requires confirmed: true to execute. |
| create_selection_strategyA | Wire a collection, eligibility rule, and ranking formula into a selection strategy. Requires confirmed: true to execute. |
| create_placementA | Create a channel placement for Experience Decisioning. Uses /exd-placements endpoint. Requires confirmed: true to execute. |
| get_offer_itemA | Look up a single offer item by its DPS ID. Read-only. |
| list_offer_itemsC | List all offer items in the ExD catalog with pagination. Read-only. |
| update_offer_itemC | Update fields on an existing offer item using JSON Patch operations. Requires confirmed: true to execute. |
| add_schema_fieldC | Add a single new field to an existing tenant fieldgroup. Requires confirmed: true to execute. |
| deprecate_schema_fieldA | Mark a custom tenant fieldgroup field as deprecated. The field remains but is flagged. For OOB Adobe fields use deprecate_oob_field. Requires confirmed: true to execute. |
| deprecate_oob_fieldA | Deprecate an OOB Adobe-managed field on the decisioning schema via a descriptor. Use for standard fields like itemDescription, itemName. For custom tenant fields use deprecate_schema_field. Requires confirmed: true. |
| detach_fieldgroupA | Safely remove a fieldgroup from the decisioning schema. Always shows a dry-run preview first. Requires confirmed: true to execute the removal. |
| get_setup_summaryA | Full read-only inventory of all ExD resources in the sandbox — offers, collections, rules, formulas, strategies, and placements. |
| lookup_decisioning_schemaB | Fetch the full resolved Personalized Offer Items decisioning schema — all fieldgroups, OOB fields, and custom tenant fields. Read-only. |
| list_schema_fieldgroupsB | List all tenant fieldgroups compatible with the Offer Item class. Read-only. |
| get_fieldgroupA | Fetch the full field definitions inside a specific fieldgroup by its altId. Read-only. |
| get_schema_audit_logB | Fetch the full audit log for the decisioning schema — every change ever made, newest first. Read-only. |
| list_schema_descriptorsC | List all descriptors on the decisioning schema — identity, deprecation, display name overrides, and relationships. Read-only. |
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 21 tools
Each tool has a distinct purpose, clearly differentiating between similar actions like deprecate_oob_field vs deprecate_schema_field, and create_offer_metadata_fieldgroup vs add_schema_field. The descriptions provide enough context to avoid confusion.
All tools follow a consistent verb_noun pattern with underscores (e.g., create_placement, list_offer_items). Mixed verbs like 'bulk_create' and 'lookup' are still clearly part of the same convention.
With 21 tools, the server covers a broad range of ExD operations without being overwhelming. The count is appropriate for a comprehensive accelerator, though slightly on the higher end.
The tool set covers creation, reading, and updating of offers and schema fields, but lacks delete tools for most resources (e.g., offers, placements, rules). Single-offer creation is also missing, relying only on bulk creation. These gaps may hinder full lifecycle management.