plausible_get_siteGet a single site by its domain (timezone, etc.). Requires an enterprise plan. Plausible: GET /api/v1/sites/{site_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| site_id | Yes | The site's domain as registered in Plausible, e.g. "example.com". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, covering the safety profile. The description adds a meaningful behavioral constraint: 'Requires an enterprise plan' (auth/permission). It also hints at the returned fields ('timezone, etc.'), though not exhaustively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose ('Get a single site by its domain') and then provide the requirement and endpoint. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one parameter and no output schema, the description covers the purpose, identifier format, and permission requirement. It doesn't detail the full response structure, but 'timezone, etc.' gives a glimpse. This is adequate for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes site_id as the domain, with an example. The description reinforces 'by its domain' but adds no new parameter semantics beyond that. Since schema coverage is 100%, baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Get' with the resource 'a single site' and the key 'by its domain', clearly distinguishing it from siblings like plausible_list_sites (which lists multiple). It also references the API endpoint, reinforcing precision.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear context for when to use it (retrieving one site's details by domain) and notes the enterprise plan requirement. However, it doesn't explicitly name alternatives like plausible_list_sites or state when not to use it, so it lacks explicit exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: aggregate, breakdown, timeseries, and realtime_visitors each serve a specific query pattern, while query_stats is the general-purpose fallback. Minor overlap exists because query_stats can reproduce what the convenience wrappers do, but descriptions clarify the intended use.
All tools share the plausible_ prefix and use lowercase with underscores, which is consistent. However, some names are single verbs/nouns (aggregate, breakdown, timeseries) rather than a uniform verb_noun pattern like list_sites, so there's a slight stylistic inconsistency.
8 tools is a well-scoped size for an analytics server. It covers the main query types (totals, breakdowns, time series, realtime) plus site and goal listing, without being bloated or insufficient.
The server covers the core analytics surface: querying metrics with aggregation, breakdown, timeseries, and realtime, plus site and goal metadata. Minor gaps exist like goal creation or site management, but these are likely outside the intended read-only analytics scope.