Skip to main content
Glama
PiwikPRO

Piwik PRO MCP Server

Official
by PiwikPRO
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

analytics_metrics_list

Read-only

List all metrics and calculated metrics usable in analytics_query_execute for a given website.

Instructions

    List available metrics for analytics queries.

    Returns all metrics that can be used as columns in analytics_query_execute.
    The format of the response:
    ```
    {"metrics": [{metric_id: metric_name}], ...}, "calculated_metrics": [{calculated_metric_id: column_name}]
    ```

    Args:
        website_id: UUID of the website/app to get metrics for

    Returns:
        MetricsList with all available metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricsYes
calculated_metricsYes

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, and the description adds the response format and return type, providing additional behavioral context beyond the annotations.

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 concise and front-loaded with purpose, though includes a code block and Args/Returns sections that could be slightly trimmed.

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?

Given an output schema exists, the description provides a sufficient overview of return format and type, making it complete for a simple list endpoint.

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?

With 0% schema coverage, the description adds minimal meaning by stating website_id is a UUID, but does not elaborate on its purpose or formatting beyond the schema.

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 description clearly states the tool lists available metrics for analytics queries and specifies they can be used as columns in analytics_query_execute, distinguishing it from sibling tools like analytics_dimensions_list.

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 implies use before executing queries by stating it returns metrics for analytics_query_execute, but no explicit when-not or alternatives are given.

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