plausible-mcp

Get Timeseries

get_timeseries

Read-onlyIdempotent

Retrieve traffic and conversion metrics over time for a site or page to spot trends and changes around deploys.

Instructions

Get traffic and conversion metrics over time for a site or specific page. Use to spot trends and changes around deploys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>",
      "date_range": "<date_range>"
    },
    "name": "get_timeseries"
  }
}

Input Schema

Name	Required	Description	Default
`goal`	No	Filter by goal name (e.g. Signup, Purchase). Do not also target event:goal in property_filters; the call is rejected.
`page`	No	Filter by page path. Exact match by default, use * as trailing wildcard (e.g. /blog*). Do not also target event:page in property_filters; the call is rejected.
`metrics`	No	Metrics to return. Defaults vary by tool. Plausible rejects these combinations: bounce_rate or visit_duration with event:goal or event:props:<name> dimensions; pageviews, events, scroll_depth or time_on_page with visit:entry_page or visit:exit_page dimensions; views_per_visit with any non-time dimension or a page filter. For goal conversions use get_conversions.
`site_id`	Yes	Plausible site domain (e.g. example.com). Required.
`date_range`	Yes	Date range: "1h", "24h" (last N hours, ending now), "7d", "30d", "12mo", "month", "year", "all", "YYYY-MM-DD,YYYY-MM-DD" (start,end, both inclusive), or "YYYY-MM-DDTHH:MM:SSZ,YYYY-MM-DDTHH:MM:SSZ" for a sub-day window (any offset, e.g. +02:00). Days after today count as zero.
`granularity`	No	Time bucket size. Use "hour" with a sub-day or few-day date_range.	day
`property_filters`	No	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.

Output Schema

Name	Required	Description
`metrics`	Yes	Metric keys, in the order they appear in each row's `metrics` array
`results`	Yes	One row per dimension-value combination returned by Plausible
`dimensions`	Yes	Dimension keys, in the order they appear in each row's `dimensions` array
`pagination`	No	Present only on paged tools (get_breakdown)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.2Nov 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed8 schema fields changedv0.10.0Oct 29, 2026

changedInput schema / properties / date_range / description

Previous value: -"Date range: \"7d\", \"30d\", \"12mo\", \"month\", \"year\", \"all\", or \"YYYY-MM-DD,YYYY-MM-DD\""New value: +"Date range: \"1h\", \"24h\" (last N hours, ending now), \"7d\", \"30d\", \"12mo\", \"month\", \"year\", \"all\", \"YYYY-MM-DD,YYYY-MM-DD\" (start,end, both inclusive), or \"YYYY-MM-DDTHH:MM:SSZ,YYYY-MM-DDTHH:MM:SSZ\" for a sub-day window (any offset, e.g. +02:00). Days after today count as zero."

changedInput schema / properties / date_range / pattern

Previous value: -"^(\\d+h|\\d+d|\\d+mo|day|month|year|all|\\d{4}-\\d{2}-\\d{2},\\d{4}-\\d{2}-\\d{2})$"New value: +"^(\\d+h|\\d+d|\\d+mo|day|month|year|all|\\d{4}-\\d{2}-\\d{2},\\d{4}-\\d{2}-\\d{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:Z|[+-]\\d{2}:\\d{2}),\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:Z|[+-]\\d{2}:\\d{2}))$"

changedInput schema / properties / goal / description

Previous value: -"Filter by goal name (e.g. Signup, Purchase)"New value: +"Filter by goal name (e.g. Signup, Purchase). Do not also target event:goal in property_filters; the call is rejected."

changedInput schema / properties / granularity / description

Previous value: -"Time bucket size"New value: +"Time bucket size. Use \"hour\" with a sub-day or few-day date_range."

changedInput schema / properties / granularity / enum

Previous value: -[
-  "day",
-  "week",
-  "month"
-]New value: +[
+  "hour",
+  "day",
+  "week",
+  "month"
+]

changedInput schema / properties / metrics / description

Previous value: -"Metrics to return. Defaults vary by tool."New value: +"Metrics to return. Defaults vary by tool. Plausible rejects these combinations: bounce_rate or visit_duration with event:goal or event:props:<name> dimensions; pageviews, events, scroll_depth or time_on_page with visit:entry_page or visit:exit_page dimensions; views_per_visit with any non-time dimension or a page filter. For goal conversions use get_conversions."

changedInput schema / properties / page / description

Previous value: -"Filter by page path. Exact match by default, use * as trailing wildcard (e.g. /blog*)"New value: +"Filter by page path. Exact match by default, use * as trailing wildcard (e.g. /blog*). Do not also target event:page in property_filters; the call is rejected."

addedOutput schema / properties / pagination

Added value: +{
+  "additionalProperties": false,
+  "description": "Present only on paged tools (get_breakdown)",
+  "properties": {
+    "has_more": {
+      "description": "True when rows exist beyond this page",
+      "type": "boolean"
+    },
+    "limit": {
+      "description": "Max rows requested",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Rows skipped before the first returned row",
+      "type": "number"
+    }
+  },
+  "required": [
+    "limit",
+    "offset",
+    "has_more"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedv0.9.0Sep 30, 2026
- removedOutput schema / properties / results / items / properties / dimensions / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / dimensions / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
- removedOutput schema / properties / results / items / properties / metrics / items / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / metrics / items / type
```
Added value: +[
+  "number",
+  "string",
+  "null"
+]
```
Changed1 schema field changedv0.7.2Aug 25, 2026
- addedInput schema / properties / property_filters / items / properties / values / items / maxLength
```
Added value: +1024
```

Changed5 schema fields changedv0.7.1Aug 6, 2026

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 / 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"
-]New value: +[
+  "site_id",
+  "date_range"
+]

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.5.1Jul 15, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds no behavioral context beyond that: no mention of how results are bucketed, request limits, or what the time-series output looks like, so it contributes little beyond the structured fields.

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?

Two short sentences with the core purpose front-loaded and no filler. It is appropriately sized, though the second sentence is thin enough that it borders on not earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool, the description is minimal, but the 100% schema coverage and the existence of an output schema carry most of the burden. The gap is guidance on choosing granularity and date_range for trend analysis, and on when compare_periods or get_breakdown would be a better fit.

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 every parameter including goal, page, metrics, date_range, granularity, and property_filters is thoroughly documented in the schema itself. The description only alludes to site versus page scoping and adds no syntax, defaults, or format detail beyond what the schema already provides, making the baseline 3 appropriate.

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 states a specific verb and resource ('get traffic and conversion metrics over time') and clarifies the scope ('for a site or specific page'), which distinguishes it from a point-in-time breakdown. It does not name a sibling tool like get_breakdown or compare_periods, so the differentiation is left implicit.

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?

'Use to spot trends and changes around deploys' implies a context for use but gives no explicit when-not conditions or named alternatives. The schema mentions using get_conversions for goal conversions, but that routing guidance lives in the parameter description rather than the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server