Skip to main content
Glama
scottehastings16

Adobe Target MCP

by scottehastings16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

listAudiences

Retrieves all available audiences from Adobe Target, providing IDs and names so you can select the right audience for activity targeting.

Instructions

List all audiences available in Adobe Target.

USAGE: Use this tool to retrieve available audiences when creating activities with audience targeting. Each audience object contains an 'id' (number) and 'name' (string) that you can display to the user.

WORKFLOW:

  1. Call this tool to get list of audiences

  2. Present audiences to user in a clear format (e.g., "1) Mobile Users (ID: 12345), 2) Desktop Users (ID: 67890)")

  3. User selects audience by name or number

  4. Extract the audience ID from the selected audience

  5. Pass the ID(s) to createActivityFromModifications via the audienceIds parameter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of audiences to return
offsetNoNumber of audiences to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states that returned objects contain 'id' and 'name' and implies a read-only list operation, but it does not explain pagination behavior, default limit/offset semantics, or any side effects. This is a meaningful gap for a tool that has limit/offset parameters yet says 'all audiences.'

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 well-structured with USAGE and WORKFLOW sections, front-loading the purpose and then giving action-able steps. Some redundancy exists (step 1 restates the first sentence), but the overall organization is effective.

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?

Although there is no output schema, the description explains the key return fields (id, name) and provides a full integration workflow ending with createActivityFromModifications. It could be more complete by addressing pagination/defaults, but it covers the core usage scenario sufficiently.

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

Parameters3/5

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

Schema description coverage is 100%, so limit and offset are already documented. The description does not add default values or clarify how the parameters interact with 'all audiences,' providing only baseline value.

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 opening sentence, 'List all audiences available in Adobe Target,' states a specific verb and resource. This clearly distinguishes it from sibling list tools like listProperties and listMboxes, and the follow-up workflow reinforces the resource and purpose.

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

Usage Guidelines4/5

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

The description explicitly states when to use it: 'when creating activities with audience targeting.' It does not mention exclusions or alternatives (e.g., when to use createAudience instead), but the intended context is clear.

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