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

plausible-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_goals

Retrieve conversion statistics for all configured goals on a website for a specified date range. Use this to monitor goal performance and track conversions.

Instructions

Get conversion stats for all configured goals on a site.

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

Input Schema

NameRequiredDescriptionDefault
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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It states the tool gets stats but does not disclose whether it is read-only, what the return format looks like, or any potential side effects. It lacks behavioral context beyond the basic action.

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, concise sentence that front-loads the action. It has no filler, but its brevity may sacrifice clarity. A bit more context could be added without hurting conciseness.

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 no output schema and limited sibling distinction, the description is incomplete. It does not clarify what 'conversion stats' includes, how the date range affects results, or how this differs from other stats tools. An agent may need additional information to use it correctly.

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 both parameters. The description adds no additional meaning beyond what is in the schema. 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 it retrieves conversion stats for all goals on a site. It uses a specific verb (Get) and resource (conversion stats for goals), which distinguishes it from siblings like get_custom_events. However, it could be more precise about the scope (e.g., 'all configured goals').

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 get_custom_events. The description does not mention prerequisites, context, or exclusion criteria.

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