Skip to main content
Glama
PiwikPRO

Piwik PRO MCP Server

Official
by PiwikPRO

apps_get

Read-only

Get complete configuration details for a specific app by providing its UUID, covering URLs, privacy settings, e-commerce tracking, and more.

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
        - e_commerce_tracking: Whether e-commerce tracking is enabled
        - delay: App delay in milliseconds
        - gdpr_enabled: Whether GDPR is enabled
        - gdpr_user_mode_enabled: Whether GDPR user mode is enabled
        - privacy_cookie_domains_enabled: Whether privacy cookie domains are enabled
        - privacy_cookie_expiration_period: Privacy cookie expiration period in seconds
        - privacy_cookie_domains: Privacy cookie domains list
        - gdpr_data_anonymization: Whether GDPR data anonymization is enabled
        - sharepoint_integration: Whether SharePoint integration is enabled
        - gdpr_data_anonymization_mode: GDPR data anonymization mode
        - privacy_use_cookies: Whether privacy mode uses cookies
        - privacy_use_fingerprinting: Whether privacy mode uses fingerprinting
        - cnil: Whether CNIL integration is enabled
        - session_id_strict_privacy_mode: Whether strict privacy mode is enabled
        - real_time_dashboards: Whether real-time dashboards are enabled
        - created_at: App creation datetime
        - updated_at: App last update datetime

    For more tracking details use `tracker_settings_app_get`.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp UUID
cnilNoWhether CNIL integration is enabled
nameYesApp name
urlsYesList of URLs where the app is available
delayNoApp delay in milliseconds
app_typeNoType of application
currencyNoApp currency
timezoneNoApp timezone
created_atNoCreation timestamp
updated_atNoLast update timestamp
gdpr_enabledNoWhether GDPR is enabled
e_commerce_trackingNoWhether e-commerce tracking is enabled
privacy_use_cookiesNoWhether privacy mode uses cookies
real_time_dashboardsNoReal-time dashboards enabled
gdpr_user_mode_enabledNoWhether GDPR user mode is enabled
privacy_cookie_domainsNoList of privacy cookie domains
sharepoint_integrationNoWhether SharePoint integration is enabled
gdpr_data_anonymizationNoGDPR data anonymization setting
privacy_use_fingerprintingNoWhether privacy mode uses fingerprinting
gdpr_data_anonymization_modeNoGDPR data anonymization mode
privacy_cookie_domains_enabledNoWhether privacy cookie domains are enabled
session_id_strict_privacy_modeNoWhether session ID strict privacy mode is enabled
privacy_cookie_expiration_periodNoPrivacy cookie expiration period in seconds
Behavior4/5

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

Annotations declare readOnlyHint: true, so the read-only nature is already known. The description adds value beyond that by detailing the return fields (e.g., id, name, urls, etc.), which provides transparency about what the tool returns. It does not mention any side effects or permissions, but none are expected for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with intro, args, returns, and a usage tip. It is front-loaded with the purpose and each sentence earns its place. No redundant or unnecessary information.

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 one parameter and an implied output schema (detailed in returns), the description is fully complete. It covers what the tool does, what to pass, what you get back, and provides a pointer to a related tool for deeper details.

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?

The single parameter 'app_id' is described as 'UUID of the app to retrieve' in the Args section, which adds specificity beyond the schema's generic type 'string' and title 'App Id'. Since schema description coverage is 0%, the description fully compensates.

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 starts with 'Get detailed information about a specific app,' which clearly states the verb and resource. It distinguishes itself from sibling tools like apps_list by specifying retrieval of a single app by ID, and even suggests an alternative tool (tracker_settings_app_get) for more tracking details.

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

Usage Guidelines5/5

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

The description includes an explicit alternative: 'For more tracking details use tracker_settings_app_get.' This clearly guides when to use this tool versus another. The context of 'specific app' versus listing all apps is implied, aiding correct invocation.

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