Skip to main content
Glama
scottehastings16

Adobe Target MCP

by scottehastings16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

createResponseToken

Create custom response tokens to include additional data in Adobe Target activity responses, enabling custom tracking and integration with analytics or tag management systems.

Instructions

Create a NEW CUSTOM response token to include data in Adobe Target activity responses.

IMPORTANT: This tool creates NEW custom tokens only. Many common tokens already exist in your account:

  • System tokens (experience.id, activity.name, geo.city, etc.) already exist with deletable: false

  • These existing tokens can only be ACTIVATED/DEACTIVATED in the Target UI (Administration > Response Tokens)

  • Use this tool to create NEW custom tokens that don't already exist

To check existing tokens, use listResponseTokens first.

Response tokens make additional data available in Target's response payload (mbox.js, at.js).

TOKEN TYPES (for creating NEW tokens):

  1. BUILT_IN - System-level tokens (e.g., experience.id, activity.name) Example: { token: "experience.id", type: "BUILT_IN" }

  2. ACTIVITY - Activity-based attributes (e.g., activity.name, campaign.id) Example: { token: "activity.name", type: "ACTIVITY" }

  3. GEO - Geographic data (e.g., geo.city, geo.country) Example: { token: "geo.city", type: "GEO" }

  4. CRS - Customer Record Service attributes Example: { token: "crs.customAttribute", type: "CRS" }

  5. MBOX - Custom mbox parameters passed in requests (MOST COMMON FOR NEW TOKENS) Example: { token: "profile.userType", type: "MBOX" } Example: { token: "profile.productId", type: "MBOX" } Note: Mbox parameters must be passed by your implementation (at.js/mobile SDK) This is the most common type for creating custom response tokens

  6. SCRIPT - Profile script outputs (e.g., profile.scriptName) Example: { token: "profile.userSegment", type: "SCRIPT" }

    IMPORTANT LIMITATION: Profile scripts CANNOT be created via the Admin API. You must create profile scripts in the Target UI first:

    • Navigate to Audiences > Profile Scripts

    • Create your script (e.g., "userSegment")

    • Then create the response token: { token: "profile.userSegment", type: "SCRIPT" }

COMMON USE CASES FOR CUSTOM TOKENS:

Custom tracking: Create tokens for your specific mbox parameters (profile.userType, profile.campaignId, etc.) Business data: Return custom business attributes in responses Integration: Pass custom data to analytics or tag management systems

BEFORE CREATING:

  1. Run listResponseTokens to check if the token already exists

  2. If it exists with deletable: false, activate it in Target UI instead

  3. If it doesn't exist, create it with this tool

WORKFLOW FOR SCRIPT TOKENS:

  1. Create profile script in Target UI (Audiences > Profile Scripts)

  2. Use this tool to create response token referencing that script

  3. Response token becomes available in Target responses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoResponse token ID (optional)
typeYesToken type - see description for details and limitations
tokenYesToken identifier (e.g., "experience.id", "profile.scriptName", "geo.city")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral disclosure burden. It does substantial work: it states the tool only creates new custom tokens, documents token types and examples, and calls out the important limitation that profile scripts cannot be created via the Admin API. It does not mention failure modes, permissions, or response behavior, which prevents a higher score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with headings, numbered workflows, and bullet lists, and the key purpose is front-loaded in the first sentence. It earns most of its length through token-type examples and limitations, though some redundancy exists between the 'IMPORTANT LIMITATION' and 'WORKFLOW FOR SCRIPT TOKENS' sections.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-complexity creation tool with no output schema and no annotations, the description is largely complete: it supplies required examples, preconditions, alternative workflows, and UI fallbacks. The main gaps are the meaning of the optional id field and any expectation about what the API returns after creation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description goes further by explaining each BUILT_IN/ACTIVITY/GEO/CRS/MBOX/SCRIPT type with concrete token examples and the mbox/profile-script implementation caveats. The optional 'id' parameter is not explained beyond the schema's 'Response token ID (optional)', so the description does not fully clarify every parameter's role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a NEW CUSTOM response token' and states the purpose: 'to include data in Adobe Target activity responses.' It clearly separates this tool from listResponseTokens and from the Target UI by emphasizing it creates new custom tokens only, so an agent can distinguish it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: run listResponseTokens first, activate existing deletable:false tokens in the Target UI, and only use this tool for tokens that do not yet exist. It also explains the profile-script case where the script must first be created in the UI, providing clear routing between API and UI workflows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools