Skip to main content
Glama
Sign In
plausible-mcp-server

plausible-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_custom_events

Retrieve a breakdown of custom events including frequency, conversion rates, and revenue for any date range and site.

Instructions

Get custom event breakdown — see which events fire most, conversion rates, and revenue.

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_custom_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoFilters like 'event:name==signup'
site_idYesThe site ID (domain)
date_rangeYesDate range: '7d', '30d', 'month', 'year'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as data freshness, permissions, pagination, or whether the operation is read-only. Only output hints are given.

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?

The description is a single sentence, concise and front-loaded. It could be more structured but is efficient.

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?

No output schema exists, so the description should explain return values. It mentions 'events fire most, conversion rates, and revenue', which provides some context but lacks detail on structure. Adequate but not thorough.

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% with all parameters described. The description does not add new meaning beyond the schema, but the schema itself is clear. Baseline 3 is appropriate.

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 clearly states the verb 'Get', the resource 'custom event breakdown', and the specific outputs: events fire most, conversion rates, revenue. It distinguishes itself from siblings like 'get_breakdown' or 'get_goals' by focusing on custom events.

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?

The description provides a basic purpose but does not explicitly guide when to use this tool versus alternatives like 'get_breakdown' or 'get_timeseries'. Usage is implied but not clearly stated.

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

Deploy Server

Other Tools