Skip to main content
Glama
PiwikPRO

Piwik PRO MCP Server

Official
by PiwikPRO

apps_get

Read-only

Retrieve detailed information about a specific app by its UUID, including name, URLs, type, timezone, currency, GDPR settings, and timestamps.

Instructions

Get detailed information about a specific app.

    Args:
        app_id: UUID of the app to retrieve

    Returns:
        Dictionary containing detailed app information including:
        - id: App UUID
        - name: App name
        - urls: List of URLs where the app is available
        - app_type: Type of application
        - timezone: App timezone
        - currency: App currency
        - gdpr_enabled: Whether GDPR is enabled
        - gdpr_data_anonymization: Whether GDPR data anonymization is enabled
        - real_time_dashboards: Whether real-time dashboards are enabled
        - created_at: App creation datetime
        - updated_at: App last update datetime

    For more details use also tracker_settings_app_get tool.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp UUID
nameYesApp name
urlsYesList of URLs where the app is available
app_typeNoType of application
timezoneNoApp timezone
currencyNoApp currency
gdpr_enabledNoWhether GDPR is enabled
gdpr_data_anonymizationNoGDPR data anonymization setting
real_time_dashboardsNoReal-time dashboards enabled
created_atNoCreation timestamp
updated_atNoLast update timestamp
Behavior4/5

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

Annotations already provide readOnlyHint=true, and the description further details the exact return fields, adding behavioral context beyond annotations. No mention of rate limits or authentication, but the read-only nature is clear.

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?

Description is structured with 'Args:' and 'Returns:' sections and a bullet list. It is front-loaded with the purpose. Could be slightly more concise, but each line provides value.

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?

Given the simple tool (one parameter, output schema provided), the description is complete: it explains the parameter, the full set of return fields, and references a related tool. No gaps.

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?

Schema coverage is 0%, but the description explicitly describes the parameter 'app_id' as 'UUID of the app to retrieve', adding type and purpose beyond the schema's 'App Id' title. This compensates for the coverage gap, though only one parameter exists.

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?

Clearly states 'Get detailed information about a specific app.' This is a specific verb+resource, distinct from the sibling 'apps_list' which lists apps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage: use when you need details on a specific app by ID. No explicit when-not or alternatives beyond mentioning 'tracker_settings_app_get' for more details. Lacks clear differentiation from similar tools.

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