Skip to main content
Glama
getsentry

plausible-mcp

by getsentry
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Breakdown

get_breakdown
Read-onlyIdempotent

Break down website analytics by dimension like page, source, or country to identify top pages and segment traffic for focused analysis.

Instructions

Break down metrics by a dimension: page, traffic source, country, device, etc. Use to find top pages, sources, or segment traffic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoFilter by page path. Exact match by default, use * as trailing wildcard (e.g. /blog*)
limitNoMax results to return
metricsNoMetrics to return. Defaults vary by tool.
site_idYesPlausible site domain (e.g. example.com). Required.
dimensionYesDimension to group results by: a standard dimension (e.g. event:page, visit:source), or a custom event property as "event:props:<name>" (e.g. event:props:plan).
date_rangeYesDate range: "7d", "30d", "12mo", "month", "year", "all", or "YYYY-MM-DD,YYYY-MM-DD"
property_filtersNoFilter results by built-in dimensions or custom event properties, e.g. [{ "property": "visit:channel", "operator": "is", "values": ["Organic Search"] }] or [{ "property": "plan", "values": ["pro"] }]. Entries are combined with AND.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricsYesMetric keys, in the order they appear in each row's `metrics` array
resultsYesOne row per dimension-value combination returned by Plausible
dimensionsYesDimension keys, in the order they appear in each row's `dimensions` array

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.7.2
    • addedInput schema / properties / property_filters / items / properties / values / items / maxLength
      Added value: +1024
  2. Changed9 schema fields changedv0.7.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / dimension / anyOf
      Added value: +[
+  {
+    "enum": [
+      "event:page",
+      "event:goal",
+      "event:hostname",
+      "visit:entry_page",
+      "visit:exit_page",
+      "visit:source",
+      "visit:referrer",
+      "visit:channel",
+      "visit:utm_medium",
+      "visit:utm_source",
+      "visit:utm_campaign",
+      "visit:utm_content",
+      "visit:utm_term",
+      "visit:device",
+      "visit:browser",
+      "visit:browser_version",
+      "visit:os",
+      "visit:os_version",
+      "visit:country",
+      "visit:region",
+      "visit:city",
+      "visit:country_name",
+      "visit:region_name",
+      "visit:city_name"
+    ],
+    "type": "string"
+  },
+  {
+    "maxLength": 312,
+    "minLength": 13,
+    "pattern": "^event:props:",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / dimension / description
      Previous value: -"Dimension to group results by"New value: +"Dimension to group results by: a standard dimension (e.g. event:page, visit:source), or a custom event property as \"event:props:<name>\" (e.g. event:props:plan)."
    • removedInput schema / properties / dimension / enum
      Removed value: -[
-  "event:page",
-  "event:goal",
-  "event:hostname",
-  "visit:entry_page",
-  "visit:exit_page",
-  "visit:source",
-  "visit:referrer",
-  "visit:channel",
-  "visit:utm_medium",
-  "visit:utm_source",
-  "visit:utm_campaign",
-  "visit:utm_content",
-  "visit:utm_term",
-  "visit:device",
-  "visit:browser",
-  "visit:browser_version",
-  "visit:os",
-  "visit:os_version",
-  "visit:country",
-  "visit:region",
-  "visit:city",
-  "visit:country_name",
-  "visit:region_name",
-  "visit:city_name"
-]
    • removedInput schema / properties / dimension / type
      Removed value: -"string"
    • addedInput schema / properties / property_filters
      Added value: +{
+  "description": "Filter results by built-in dimensions or custom event properties, e.g. [{ \"property\": \"visit:channel\", \"operator\": \"is\", \"values\": [\"Organic Search\"] }] or [{ \"property\": \"plan\", \"values\": [\"pro\"] }]. Entries are combined with AND.",
+  "items": {
+    "properties": {
+      "operator": {
+        "default": "is",
+        "description": "Match operator: is, is_not, contains, contains_not (default: is)",
+        "enum": [
+          "is",
+          "is_not",
+          "contains",
+          "contains_not"
+        ],
+        "type": "string"
+      },
+      "property": {
+        "description": "What to filter on: a built-in dimension (e.g. \"visit:channel\", \"visit:source\", \"event:page\") or a custom event property as its bare name (e.g. \"plan\" targets event:props:plan)",
+        "maxLength": 312,
+        "minLength": 1,
+        "type": "string"
+      },
+      "values": {
+        "description": "One or more values to match the property against",
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      }
+    },
+    "required": [
+      "property",
+      "values"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / site_id / description
      Previous value: -"Plausible site domain (e.g. example.com). Uses PLAUSIBLE_DEFAULT_SITE_ID if omitted."New value: +"Plausible site domain (e.g. example.com). Required."
    • changedInput schema / required
      Previous value: -[
-  "date_range",
-  "dimension"
-]New value: +[
+  "site_id",
+  "date_range",
+  "dimension"
+]
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.5.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safety and repeatability profile. The description adds no behavioral details (e.g., pagination, limits, or mutation effects). Since annotations cover safety, the bar is lower, but the description contributes no extra behavioral context beyond the generic 'break down' phrasing.

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?

Two sentences with zero waste. The core action is front-loaded ('Break down metrics by a dimension'), followed by a practical usage note. Every element earns its place; no redundancy or filler.

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?

Despite having 7 parameters, all are described in the schema, and an output schema exists (as per context signals). The description provides enough context for an agent to know when to call this tool, relying on the schema for parameter details and the output schema for return structure. It could mention limits or filters, but those are already in the schema. The description is adequate for this complexity.

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?

Schema description coverage is 100%, so all 7 parameters have detailed descriptions in the schema. The tool description mentions 'dimension' generically and the purpose, but doesn't add any parameter-specific information beyond the schema. With high schema coverage, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: 'Break down metrics by a dimension' and lists example dimensions (page, source, country). It conveys the purpose without tautology. While it doesn't explicitly differentiate from siblings like get_timeseries or get_conversions, the concept of dimension-based grouping is distinct enough for an agent to infer usage.

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 provides clear usage context: 'Use to find top pages, sources, or segment traffic.' It tells the agent when to apply the tool, but doesn't explicitly state when not to use it or name alternative tools. This matches the 'clear context, no exclusions' tier.

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/getsentry/plausible-mcp'

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