Adobe CJA

Returns metadata for a given metric

describeMetric

Shows details about a workspace project, including its definition, data view, and owner. Use to inspect a project before modifying it with upsertProject, so its existing panels can be carried forward instead of dropped.

describeProject

Returns metadata for a given segment, including its definition, compatibility, and owner. Use to inspect a segment before modifying it with upsertSegment.

describeSegment

Finds audiences available to the user. Returns a paginated list useful for discovering audience IDs for describeAudience or upsertAudience. By default lists only audiences visible to the current user; pass includeType=all to list all organization audiences, which requires the CJA product administrator role.

findAudiences

Finds calculated metrics. Use for calculated metrics specifically—standard metrics are in findMetrics. Default to semantic search: pass searchQuery to get relevance-ranked results (requires a session data view). Only omit searchQuery when you need the full paged list. Hidden calculated metrics are excluded by default; set includeHidden=true to include them.

findCalculatedMetrics

Finds data views accessible to the user. Use to discover available data views or obtain a data view ID for setDefaultSessionDataViewId.

findDataViews

Finds saved date range components available to the user. Returns a paginated list useful for discovering reusable date ranges or obtaining a date range ID for use in a project definition.

findDateRanges

Finds dimensions available for the given data view. Hidden dimensions are excluded by default; set includeHidden=true to include them. Default to semantic search first: pass searchQuery with a topic or purpose (e.g. 'date time', 'page', 'user') to get relevance-ranked dimensions with a score per result. Only omit searchQuery when you need a full paged list of all dimensions (page, limit).

findDimensions

Finds available metrics (standard and custom from the data view). Hidden metrics are excluded by default; set includeHidden=true to include them. Does NOT include calculated metrics—use findCalculatedMetrics for those. Default to semantic search first: pass searchQuery with a topic or purpose (e.g. 'sessions visits', 'revenue', 'conversions') to get relevance-ranked metrics with a score. Only omit searchQuery when you need the full metric list.

findMetrics

Finds workspace projects. To list the user's own projects ("my projects", "what projects do I have"), call with no searchTerm — returns projects they own or that are shared with them. To locate a specific project the user describes by text, pass searchTerm — this searches across all projects in the org and fuzzy-matches (by default on name; use searchFields to match owner/tag/data-view names instead). Filters stack on either mode: filterByApproved (approved/governed), filterByFavorites (starred, user-scoped), filterByModifiedAfter (recently changed). When the user refers to a data view, owner, tag, segment, or calculated metric already established earlier in the conversation, reuse its ID as filterByDataIds / filterByOwnerIds / filterByTagIds / (filterByUsesComponentType+filterByUsesComponentId) rather than searching by name. Returns a paginated list useful for discovering project IDs for describeProject or upsertProject.

findProjects

Finds segments available to the user. Semantic search requires a session data view; omit searchQuery when you need a full paged list of all segments.

findSegments

Returns a ranked list of suggested starter questions tailored to the user's most-used components in a data view, suitable for priming an AI conversation about their data.

getStarterQuestions

Returns the data view ID set for the current session via setDefaultSessionDataViewId. Use the expansions parameter to also return the data view's name and description.

getCurrentDataView

Returns the authoritative current date and time from the MCP server clock. Call this before converting relative phrases like 'last 30 days' or 'this month' into runReport ISO 8601 startDate/endDate, and whenever you need today's date. Do not rely on your training cutoff for the current date.

getServerDateTime

Lists components of a specified type ranked by reporting usage frequency. Useful for discovering popular dimensions, metrics, or segments.

listComponentUsage

Lists components frequently used together in reports with a specified component. Useful for discovering natural pairings for report building.

listFrequentlyUsedWith

Lists components similar to a specified component. Useful for finding alternatives or related dimensions, metrics, or segments.

listSimilarTo

Runs a ranked report with support for single or multiple dimensions and metrics. For multi-dimension/metric reports, all are reported together in a single request. Dimensions are assigned columnIds starting from '0' in the order provided. Metrics are also assigned columnIds starting from '0' in the order provided. By default, results are sorted by the first metric in descending order. Sorting by a dimension is only supported for single-dimension reports; multi-dimension reports must be sorted by a metric. Supports breakdown reports via the optional 'breakdowns' parameter — call describeCja(BREAKDOWN_GUIDE) for full instructions on when and how to use breakdowns.

runReport

Runs a report that gets the top dimension items for the given dimension. Example dimension items: Dimension=Country, Items=US, UK, Canada, etc.

searchDimensionItems

Sets the default data view ID for the current session. Once set, other tools that accept a dataViewId parameter can omit it. The default persists for up to 8 hours.

setDefaultSessionDataViewId

Submits a single piece of feedback about CJA MCP tools, tied to the user prompt that triggered it. Proactively call this whenever a CJA MCP tool returns an error or fails to behave as described — including repeated or recurring errors — without waiting for the user to ask. Also submit feedback on the user's behalf whenever they express it — either explicitly (asking to submit, share, or report feedback, including suggestions, complaints, or praise) or implicitly (complaining about or criticizing a tool, a result, or how a response looks or reads) — even if they never use the word 'feedback'. Capture their concern faithfully; do not invent feedback the user did not express. Call this tool once per user prompt that warrants feedback. Submit feedback as soon as an issue or observation occurs — do not wait until the end of the conversation, as context is freshest immediately after the relevant prompt. IMPORTANT — DO NOT include any Personally Identifiable Information (PII) such as names, email addresses, phone numbers, physical addresses, or any data that can identify a specific individual (such as reporting data returned from an earlier reporting tool call). DO NOT include actual reporting data values (row-level data, metric values from reports, or dimension item values). You MAY include component metadata such as component IDs (e.g. 'metrics/visits'), XDM schema paths, data view IDs, segment/calculated-metric definitions, and tool parameter values — these are safe to share. Before submitting, review all content to confirm no PII or sensitive reporting data is present.

submitFeedbackOrReportError