Skip to main content
Glama
AVIMBU

Plausible MCP Server

by AVIMBU

plausible_query

Query website analytics data from Plausible to retrieve metrics like visitors, pageviews, bounce rate, and conversion rates for specific sites and date ranges.

Instructions

Query analytics data from Plausible

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesThe domain of the site to query data for
metricsYesString list of metrics to query with the following options: 'visitors' 'int' The number of unique visitors | 'visits' 'int' The number of visits/sessions | 'pageviews' 'int' The number of pageview events | 'views_per_visit' 'float' The number of pageviews divided by the number of visits. | 'bounce_rate' 'float' Bounce rate percentage | 'visit_duration' 'int' Visit duration in seconds | 'events' 'int' The number of events (pageviews + custom events). When filtering by a goal, this metric corresponds to 'Total Conversions' in the dashboard. | 'scroll_depth' 'int' Page scroll depth averaged per session Requires event:page filter or dimension being set | 'percentage' 'float' The percentage of visitors of total who fall into this category Requires non-empty dimensions | 'conversion_rate' 'float' The percentage of visitors who completed the goal. Requires non-empty dimensions, event:goal filter or dimension being set | 'group_conversion_rate' 'float' The percentage of visitors who completed the goal with the same dimension. Requires: dimension list passed, an event:goal filter or event:goal dimension Requires non-empty dimensions, event:goal filter or dimension being set | 'average_revenue' 'Revenue' or null Average revenue per revenue goal conversion Requires revenue goals, event:goal filter or dimension for a relevant revenue goal. | 'total_revenue' 'Revenue' or null Total revenue from revenue goal conversions Requires revenue goals, event:goal filter or dimension for a relevant revenue goal.
date_rangeYesDate range for the query, with the following options: ["2024-01-01", "2024-07-01"] Custom date range (ISO8601) | ["2024-01-01T12:00:00+02:00", "2024-01-01T15:59:59+02:00"] Custom date-time range (ISO8601) | "day" Current day (e.g. 2024-07-01) | "7d" Last 7 days relative to today | "30d" Last 30 days relative to today | "month" Since the start of the current month | "6mo" Last 6 months relative to start of this month | "12mo" Last 12 months relative to start of this month | "year" Since the start of this year | "all"

Implementation Reference

  • Handler logic for the plausible_query tool in the CallToolRequest handler. Validates input arguments and delegates to plausibleClient.query.
    case "plausible_query": {
      const args = request.params.arguments as unknown as QueryArgs;
      if (!args.site_id || !args.metrics || !args.date_range) {
        throw new Error(
          "Missing required arguments: site_id, metrics, and date_range"
        );
      }
      const response = await plausibleClient.query(
        args.site_id,
        args.metrics,
        args.date_range
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition for plausible_query, including input schema with properties for site_id, metrics, and date_range.
    export const queryTool: Tool = {
      name: "plausible_query",
      description: "Query analytics data from Plausible",
      inputSchema: {
        type: "object",
        required: ["site_id", "metrics", "date_range"],
        properties: {
          site_id: {
            type: "string",
            description: "The domain of the site to query data for",
          },
          metrics: {
            type: "array",
            items: {
              type: "string",
            },
            description:
              "String list of metrics to query with the following options: 'visitors' 'int' The number of unique visitors | 'visits' 'int' The number of visits/sessions | 'pageviews'	'int' The number of pageview events	 | 'views_per_visit'	'float' The number of pageviews divided by the number of visits.	 | 'bounce_rate'	'float' Bounce rate percentage	 | 'visit_duration'	'int' Visit duration in seconds	 | 'events'	'int' The number of events (pageviews + custom events). When filtering by a goal, this metric corresponds to 'Total Conversions' in the dashboard.	 | 'scroll_depth'	'int' Page scroll depth averaged per session	Requires event:page filter or dimension being set | 'percentage'	'float' The percentage of visitors of total who fall into this category	Requires non-empty dimensions | 'conversion_rate'	'float' The percentage of visitors who completed the goal.	Requires non-empty dimensions, event:goal filter or dimension being set | 'group_conversion_rate'	'float' The percentage of visitors who completed the goal with the same dimension. Requires: dimension list passed, an event:goal filter or event:goal dimension	Requires non-empty dimensions, event:goal filter or dimension being set | 'average_revenue'	'Revenue' or null	Average revenue per revenue goal conversion	Requires revenue goals, event:goal filter or dimension for a relevant revenue goal. | 'total_revenue'	'Revenue' or null	Total revenue from revenue goal conversions	Requires revenue goals, event:goal filter or dimension for a relevant revenue goal.",
          },
          date_range: {
            type: "string",
            description:
              'Date range for the query, with the following options: ["2024-01-01", "2024-07-01"] Custom date range (ISO8601) | ["2024-01-01T12:00:00+02:00", "2024-01-01T15:59:59+02:00"] Custom date-time range (ISO8601) | "day"	Current day (e.g. 2024-07-01) | "7d"	Last 7 days relative to today | "30d"	Last 30 days relative to today | "month" Since the start of the current month | "6mo" Last 6 months relative to start of this month | "12mo" Last 12 months relative to start of this month | "year" Since the start of this year | "all"',
          },
        },
      },
    };
  • src/index.ts:24-28 (registration)
    Registration of the plausible_query tool in the ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [queryTool],
      };
    });
  • Core implementation of the query logic in PlausibleClient, performing the POST request to the Plausible API.
    async query(siteId: string, metrics: string[], dateRange: string) {
      const response = await fetch(`${PLAUSIBLE_API_URL}/query`, {
        method: "POST",
        headers: {
          Authorization: `Bearer ${PLAUSIBLE_API_KEY}`,
          "Content-Type": "application/json",
        },
        body: JSON.stringify({
          site_id: siteId,
          metrics: metrics,
          date_range: dateRange,
        }),
      });
    
      if (!response.ok) {
        throw new Error(`Plausible API error: ${response.statusText}`);
      }
    
      return response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only query, requires authentication, has rate limits, or what the output format might be. 'Query' implies read-only, but this isn't explicitly stated, leaving gaps in understanding the tool's behavior.

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, efficient sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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's complexity (3 required parameters, no output schema, no annotations), the description is insufficient. It doesn't explain what the query returns, error conditions, or usage constraints, leaving the agent with incomplete context for effective tool selection and invocation.

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?

The schema description coverage is 100%, providing detailed documentation for all parameters (site_id, metrics, date_range). The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline for high schema coverage without compensating value.

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 action ('Query') and resource ('analytics data from Plausible'), making the purpose evident. It doesn't need sibling differentiation since there are no sibling tools, but it could be more specific about what type of analytics data (e.g., metrics, dimensions, filters).

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or typical use cases. It's a generic statement that doesn't help an agent understand the appropriate context for invocation.

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

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