Skip to main content
Glama
markhilton
by markhilton

cja_run_breakdown_report

Run a multi-dimensional breakdown report to analyze a primary dimension broken down by a secondary dimension, revealing distribution patterns and relationships.

Instructions

Run a multi-dimensional breakdown report.

This tool performs breakdown analysis where you analyze a primary dimension and further break it down by a secondary dimension. For example, analyze pages and break them down by device type to understand device distribution per page.

Args: primary_dimension: Primary dimension ID (e.g., 'variables/page', 'variables/campaign'). breakdown_dimension: Dimension to break down by (e.g., 'variables/mobiledevicetype'). metrics: List of metric IDs to analyze. start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. limit: Maximum number of primary dimension items (default: 10, max: 500). breakdown_limit: Maximum breakdown items per primary item (default: 5, max: 50). segment_ids: Optional list of segment IDs to filter the report. dataview_id: Optional data view ID (uses configured default if not provided).

Returns: Dictionary with nested breakdown report results.

Example queries: - "Break down top pages by device type" - "Show me campaigns broken down by browser for last month" - "Analyze product performance by marketing channel"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
primary_dimensionYes
breakdown_dimensionYes
metricsYes
start_dateYes
end_dateYes
limitNo
breakdown_limitNo
segment_idsNo
dataview_idNo
Behavior3/5

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

No annotations provided; description covers what the tool does (breakdown analysis, returns nested results) but lacks explicit mention of read-only nature, side effects, or rate limits.

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?

Well-structured with summary, args, returns, and examples. Contains some redundancy but overall concise and informative.

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

Completeness5/5

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

Covers all parameters, usage context, and return format. Given no output schema, the description is sufficiently complete for agent understanding.

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?

Input schema has 0% description coverage, but description compensates by explaining each parameter's purpose, including examples and default values.

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?

Description clearly states it runs a breakdown report with primary and secondary dimensions. Examples differentiate from sibling tools like cja_run_report and cja_run_trended_report.

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?

Provides clear usage context with example queries and parameter explanations. Does not explicitly state when not to use, but sibling tool names imply alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markhilton/adobe-cja-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server