Skip to main content
Glama
The-Focus-AI

Plausible MCP

by The-Focus-AI

get_breakdown

Retrieve granular website analytics breakdowns segmented by page, source, country, or device, with customizable metrics and filters for targeted insights.

Instructions

Get detailed analytics breakdown for a site.

COMMON QUERIES:

  1. Most visited pages in last 7 days: {"site_id": "example.com", "metrics": ["visitors", "pageviews"], "dimensions": ["event:page"], "date_range": "7d"}

  2. Traffic sources with bounce rates: {"site_id": "example.com", "metrics": ["visitors", "bounce_rate"], "dimensions": ["visit:source"], "date_range": "30d"}

  3. Geographic breakdown: {"site_id": "example.com", "metrics": ["visitors", "visit_duration"], "dimensions": ["visit:country", "visit:city"], "date_range": "month"}

  4. Hourly visitor trends for today: {"site_id": "example.com", "metrics": ["visitors", "pageviews"], "dimensions": ["time:hour"], "date_range": "day"}

  5. Device and browser analysis: {"site_id": "example.com", "metrics": ["visitors", "bounce_rate"], "dimensions": ["visit:device", "visit:browser"], "date_range": "7d"}

  6. Campaign performance: {"site_id": "example.com", "metrics": ["visitors", "views_per_visit"], "dimensions": ["visit:utm_campaign", "visit:utm_source"], "date_range": "month"}

AVAILABLE METRICS:

  • visitors: Number of unique visitors

  • visits: Number of visits/sessions

  • pageviews: Number of pageview events

  • views_per_visit: Average number of pages viewed per visit

  • bounce_rate: Percentage of visits with only one page view

  • visit_duration: Average visit duration in seconds

  • events: Total number of events (pageviews + custom events)

AVAILABLE DIMENSIONS: Event dimensions (page/content related):

  • event:name - Event name (e.g., 'pageview', 'download', etc.)

  • event:page - Full page URL including UTM parameters

  • event:page.pathname - Page path without query parameters

  • event:props:* - Custom event properties (e.g., event:props:author)

Visit dimensions (visitor/session related):

  • visit:source - Traffic source (e.g., 'Google', 'Twitter')

  • visit:referrer - Full referrer URL

  • visit:utm_medium - Marketing medium (e.g., 'cpc', 'social')

  • visit:utm_source - UTM source parameter

  • visit:utm_campaign - UTM campaign name

  • visit:utm_content - UTM content parameter

  • visit:utm_term - UTM term parameter

  • visit:device - Device type (desktop, mobile, tablet)

  • visit:browser - Browser name

  • visit:browser_version - Browser version

  • visit:os - Operating system

  • visit:os_version - OS version

  • visit:country - Country of visitor

  • visit:country_name - Full country name

  • visit:region - Region/state of visitor

  • visit:region_name - Full region/state name

  • visit:city - City of visitor

  • visit:city_name - Full city name

Time dimensions (for trends and patterns):

  • time:minute - Group by minute (only available with 'day' time:day range)

  • time:hour - Group by hour (only available with 'day' time:day range)

  • time:day - Group by day (available with any time:day range)

  • time:week - Group by week (available with 'month', '6mo', '12mo', or custom ranges)

  • time:month - Group by month (available with '6mo', '12mo', or custom ranges)

Note: Time dimensions are mutually exclusive - only one can be used at a time. When using time dimensions, results are automatically sorted chronologically.

FILTERING EXAMPLES:

  1. Only Chrome users: {"filters": [["is", "visit:browser", ["Chrome"]]]}

  2. Blog pages only: {"filters": [["contains", "event:page", ["/blog"]]]}

  3. Multiple countries: {"filters": [["is", "visit:country", ["US", "GB", "CA"]]]}

  4. Exclude certain pages: {"filters": [["is_not", "event:page", ["/admin", "/login"]]]}

  5. Complex filter (Chrome users from US): {"filters": [["and", [["is", "visit:browser", ["Chrome"]], ["is", "visit:country", ["US"]]]]]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesYour website domain as configured in Plausible (e.g., 'example.com')
metricsNoList of metrics to calculate. Default: ['visitors']. See AVAILABLE METRICS above for options.
dimensionsNoProperties to group results by. Default: ['time:day']. See AVAILABLE DIMENSIONS above for options. 'date' is not a valid dimension
date_rangeNoTime period to analyze. Options: - 'day': Last 24 hours - '7d', '30d': Last N days - 'month': Current month - '6mo', '12mo': Last N months - Custom ISO dates: ['2024-01-01', '2024-01-31'] Default: '7d'
filtersNoFilter conditions to apply. See FILTERING EXAMPLES above. Operators: is, is_not, contains, contains_not, matches, matches_not
limitNoMaximum number of results to return. Default: 10000
pageNoPage number for pagination. Default: 1
Behavior4/5

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

No annotations are provided, so the description bears full burden. It details available metrics, dimensions, filtering operators, and constraints like time dimension mutual exclusivity. It could mention rate limits or data freshness but is otherwise transparent.

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 clear sections (COMMON QUERIES, AVAILABLE METRICS, etc.) and front-loaded purpose. However, it is somewhat lengthy due to many examples; could be slightly more concise.

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 the tool's complexity (7 parameters, no output schema), the description covers parameters, filtering, and available values comprehensively. Missing explicit return structure but still very complete.

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 100% with good descriptions. The description adds significant value by listing available metrics/dimensions, providing filtering examples, and explaining parameters 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?

Description clearly states 'Get detailed analytics breakdown for a site' with specific verb and resource. It distinguishes from siblings like get_traffic by focusing on breakdowns with dimensions and metrics.

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 extensive examples and common queries that implicitly guide usage. However, it does not explicitly state when to use alternatives or exclude inappropriate use cases.

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/The-Focus-AI/plausible-mcp'

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