Create targeted audiences for Adobe Target by defining a name, targeting rules, and description. Enables natural language audience creation for personalized experiences.
Create a new audience
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Audience name | |
| targetRule | No | Audience targeting rules | |
| description | No | Audience description |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'create', offering no information about persistence, idempotency, duplicate handling, validation of targetRule, permissions, or response behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, but it is under-specified and duplicates the tool name. It does not earn its place because it contributes no information beyond what the name already conveys.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, no annotations, a nested targetRule object, and a long list of sibling tools. The description leaves the agent with no guidance on targetRule shape, return values, or invocation context, making it inadequate for a tool with this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3 even though the description adds no parameter-level meaning. The description does not clarify how targetRule should be structured, but that is not its responsibility given complete schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Create a new audience' restates the tool name exactly and provides no additional detail about what creating an audience entails. It is not misleading, but it is tautological and does not help distinguish this operation from other create-type siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as listAudiences or createABActivity. No prerequisites, exclusions, or practical context are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.