Skip to main content
Glama
plausible-mcp

plausible-mcp

by getsentry

Get Conversions

get_conversions
Read-onlyIdempotent

Retrieve goal conversion rates and counts for a Plausible site, optionally breaking results down by page to identify which pages drive conversions.

Instructions

Get goal conversion rates and counts. Can break down by page to see which pages drive conversions.

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

Input Schema

NameRequiredDescriptionDefault
goalNoFilter by goal name (e.g. Signup, Purchase). Do not also target event:goal in property_filters; the call is rejected.
pageNoFilter 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.
site_idYesPlausible site domain (e.g. example.com). Required.
date_rangeYesDate 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.
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.
breakdown_by_pageNoIf true, adds event:page and each page's group_conversion_rate: the percent of that page's visitors who converted

Output Schema

NameRequiredDescriptionDefault
notesNoFacts about this result that change how to read its numbers
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
paginationNoPresent only on paged tools (get_breakdown)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.0
    • changedInput schema / properties / breakdown_by_page / description
      Previous value: -"If true, shows conversion rate per page"New value: +"If true, adds event:page and each page's group_conversion_rate: the percent of that page's visitors who converted"
    • addedOutput schema / properties / notes
      Added value: +{
      +  "description": "Facts about this result that change how to read its numbers",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changedv0.12.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed5 schema fields changedv0.10.0
    • 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 / 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"
      +}
  4. Changed4 schema fields changedv0.9.0
    • 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"
      +]
  5. Changed1 schema field changedv0.7.2
    • addedInput schema / properties / property_filters / items / properties / values / items / maxLength
      Added value: +1024
  6. Changed5 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 / 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"
  7. First observedv0.5.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and behavior profile is covered without the description. The description adds a light hint about the business meaning of the page breakdown, but it neither repeats nor contradicts the schema's own full explanation of breakdown_by_page and adds little beyond it. No contradiction with the annotations exists.

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, both of which carry information, and the main purpose is stated first. Nothing is padded or repeated, though the second sentence could be merged to avoid restating the schema.

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?

Given that the input schema is fully documented, an output schema exists, and the annotations cover the behavioral profile, the definition is adequate for correct invocation. It remains incomplete regarding routing among the breakdown and timeseries siblings, which is the one thing the structured fields cannot supply.

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 the schema already documents site_id, date_range, goal, page, property_filters, and breakdown_by_page, including the explicit 'do not also target event:goal/event:page' guards. The description contributes no additional parameter semantics; the baseline score 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?

States a specific verb and resource: retrieving goal conversion rates and counts, plus an optional per-page breakdown. This is clear, but it does not distinguish the tool from the sibling get_breakdown, even though it also performs a page breakdown; an agent could reasonably hesitate between the two.

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?

Usage is only implied: the agent can infer it should call this tool whenever it wants conversion metrics, and the second sentence hints that a page breakdown exists. There is no explicit when-to-use versus when-not, and no mention of get_breakdown, get_timeseries, or compare_periods as alternatives.

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