01 · Records and state owned
Report suites, dimensions, metrics, segments, ranked/trended reports, workspace components
Adobe
Adobe Analytics
Curated anchor platform in digital analytics with material relevance to the Marcom operating stack and a first-party developer surface.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Report suites, dimensions, metrics, segments, ranked/trended reports, workspace components
03 · Actions and write paths
Manage supported segments and date ranges and create/run ranked or trended reports. Do not infer permission to alter report-suite administration or unrelated Analytics configuration.
04 · Authentication and permissions
Adobe identity and the connected Analytics product/report-suite permissions control access to report suites, components, segments, date ranges, projects and reports.
05 · Monitoring, approval, and recovery
Preserve report-suite boundaries, metric and segment definitions, date ranges, component ownership and report provenance; confirm before changing shared segments or date ranges.
06 · Gaps and implementation limits
The public MCP overview lists component discovery, reporting, segment/date-range management and workspace exploration; use the current tool reference for exact parameters and availability.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
Verified first-party provider MCPAdobe-hosted remote MCPGenerally documented service
Role: provider
Read scope: Report suites, dimensions, metrics, segments, ranked/trended reports, workspace components
Write scope: The hosted server can manage segments and date ranges and can create/run ranked or trended reports; no broader Analytics administration write scope is inferred.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Adobe ships these experiences.
Single-platform patterns
- Digital-performance and anomaly investigation cockpit
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Adobe Analytics + warehouse or semantic layer: executive insight brief
- Adobe Analytics + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
MCP / agent-role validationRepresentative source
https://developer.adobe.com/analytics-mcp/docs/aa/ ↗Official Adobe documentation provides hosted endpoint and tool scope.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
MCPSource inventory
https://developer.adobe.com/analytics-mcp/docs/ ↗First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
APISource inventory
https://developer.adobe.com/analytics-apis/docs/2.0/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://business.adobe.com/products/adobe-analytics.html ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.