Skip to main content
Glama

Pirsch Analytics MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Get total visitors

pirsch_get_totals
Read-only

Totals for a period: visitors, views, sessions, bounces, bounce rate and conversion rate. Not grouped by day, so returning visitors are counted once. GET /api/v1/statistics/total.

Input Schema

NameRequiredDescriptionDefault
osNoOperating system. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
toYesLast day, yyyy-mm-dd, whole day included.
tzNoIANA time zone such as Europe/Berlin. Default: the dashboard's time zone.
tagNoTag key to filter for.
cityNoCity name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
fromYesFirst day, yyyy-mm-dd (in the dashboard time zone unless tz is set).
pathNoPage path, for example /pricing. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
tagsNoTag key/value pairs; only results with all pairs match.
eventNoEvent name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
browserNoBrowser. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
channelNoTraffic channel such as "Paid Search" or "Organic Search". Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
countryNoISO 3166 alpha-2 country code such as jp. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
patternNoRegular expression that filters and groups pages, for example (?i)^/blog/[^/]+$.
hostnameNoHostname (useful for rollup views). Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
languageNoISO 639-1 language code such as en. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
platformNoPlatform.
referrerNoReferrer, usually a URL. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_termNoUTM term. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
domain_idYesPirsch domain (dashboard) id. Get it from pirsch_list_domains.
exit_pathNoExit page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
entry_pathNoEntry page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
event_metaNoEvent metadata key/value pairs; only events with all pairs match.
utm_mediumNoUTM medium. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_sourceNoUTM source. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_contentNoUTM content. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
screen_classNoScreen class XXL, XL, L, M or S. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_campaignNoUTM campaign. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
referrer_nameNoReferrer name, usually the hostname. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe read profile (readOnlyHint=true, destructiveHint=false), so the description only needs to add semantics — and it does, disclosing the aggregation behavior that returning visitors are counted once. It does not describe response shape, but the metric enumeration covers most of what an agent needs.

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?

Three short clauses front-load the returned metrics, then the aggregation caveat, then the endpoint. No filler, and the most decision-relevant information comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the returned fields, and the aggregation note clarifies how to read them. For a 28-param, fully-documented filter surface, this is complete enough, though pagination/format details are absent.

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% across all 28 parameters, so the schema already documents filters, formats, and negation prefixes. The description adds no parameter-level detail, which is acceptable given the schema does the heavy lifting — baseline 3.

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+resource (totals for a period) and enumerates the exact metrics returned (visitors, views, sessions, bounces, bounce rate, conversion rate). The 'not grouped by day' clause implicitly distinguishes it from the time-series sibling, though no sibling is named explicitly.

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 through the 'not grouped by day' contrast with a day-series tool; there is no explicit when-to-use/when-not statement and no prerequisites beyond the required params. Adequate but leaves the agent to infer when totals beat the time-series alternative.

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

All Pirsch Analytics MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources