plausible-mcp-server

get_timeseries

Retrieve time-series data for website metrics like visitors and pageviews, with customizable intervals from hourly to monthly.

Instructions

Get time-series data for one or more metrics — daily, hourly, weekly, or monthly intervals.

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>",
      "metrics": "<metrics>",
      "date_range": "<date_range>"
    },
    "name": "get_timeseries"
  }
}

Input Schema

Name	Required	Description
`filters`	No	Filters to apply
`metrics`	Yes	Metrics: visitors, visits, pageviews, events, bounce_rate, visit_duration
`site_id`	Yes	The site ID (domain)
`interval`	No	Interval: 'date' (default), 'month', 'week', 'hour' (last 24h only)
`date_range`	Yes	Date range: '7d', '30d', 'month', 'year', or 'YYYY-MM-DD,YYYY-MM-DD'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Get time-series data', implying a read operation, but omits details like rate limits, data freshness, maximum metrics, or response format.

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 a single concise sentence that front-loads the purpose and key functionality. No filler or redundant information.

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

Completeness2/5

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

Given the tool has 5 parameters and no output schema, the description is too sparse. It does not explain the return format, date range syntax details, or filtering capabilities, leaving significant gaps for an agent.

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 coverage is 100%, so the schema already documents all parameters. The description adds 'daily, hourly, weekly, or monthly intervals' which mirrors the schema but does not provide additional meaning. Baseline 3 is 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 clearly states the tool retrieves time-series data for metrics with various intervals, specifying verb and resource. However, it does not explicitly distinguish from sibling tools like query_stats or get_breakdown, leaving the agent to infer differentiation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like query_stats or realtime_visitors. The description lacks context for optimal usage, making it hard for an agent to select appropriately.

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

Deploy Server