Skip to main content
Glama
PiwikPRO

Piwik PRO MCP Server

Official
by PiwikPRO

analytics_custom_dimensions_list

Read-only

Retrieve a list of custom dimensions for a website, optionally filtered by scope (session, event, or product).

Instructions

    List custom dimensions, optionally filtered by scope.

    Args:
        website_id: Website/App UUID
        scope: Optional scope filter:
               - "session": Returns only session-scoped dimensions
               - "event": Returns only event-scoped dimensions
               - "product": Returns only product dimensions
               - None (default): Returns both standard and product dimensions separately
        limit: Maximum number of rows to return (default: 10, min: 1, max: 100000)
               Note: Only applies to standard dimensions (session/event). Product dimensions
               are not paginated by the API.
        offset: Number of rows to skip (default: 0, min: 0)
               Note: Only applies to standard dimensions (session/event).

    Returns:
        - If scope is "session" or "event": CustomDimensionsList (filtered by scope)
        - If scope is "product": ProductCustomDimensionsList
        - If scope is None: UnifiedCustomDimensionsList with both standard and product dimensions

    Raises:
        RuntimeError: If API request fails
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYes
scopeNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds behavioral details about pagination limits for standard vs product dimensions and return types per scope, but omits authentication or rate limit info.

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 args/returns/raises, front-loaded purpose, but somewhat verbose. Could be slightly more concise.

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 parameter behavior, return types per scope, edge cases (product pagination), and error handling. Output schema exists, so return value explanation is adequate.

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

Parameters5/5

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

Input schema has 0% description coverage; description compensates with full explanations for scope enum, limit/offset defaults and special behavior for product dimensions.

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 lists custom dimensions with optional scope filter. Distinguishes from sibling tools like analytics_custom_dimensions_get (single dimension) and analytics_dimensions_list (different resource type).

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 guidance on scope parameter usage and defaults, but does not explicitly state when not to use or mention alternatives among siblings.

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/PiwikPRO/mcp'

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