Skip to main content
Glama

Pirsch Analytics MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Get time spent

pirsch_get_duration
Read-only

Average session duration over time, or average time on page over time, in seconds. GET /api/v1/statistics/duration/session or /duration/page.

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).
kindYessession = average session duration, page = average time on page.
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).
scaleNoGroup results by day (default), week, month or year.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine value with the unit ('in seconds') and the underlying endpoints, but omits return shape, aggregation behavior or pagination. Adequate but not rich.

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 tight sentences, front-loaded with the output meaning before the endpoint paths. The endpoint mention is marginally useful but slightly technical clutter; still efficient overall.

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?

For a 30-parameter statistics tool with nested objects and no output schema, the description is thin. Annotations carry the safety profile and the schema carries the params, but the description says nothing about the time-series shape or scale interaction that an agent would need to interpret results.

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 all 30 parameters including the kind enum and filter syntax. The description restates the kind semantics but adds no detail beyond the schema, which is the expected baseline of 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 ('Average session duration over time, or average time on page over time') and distinguishes the two modes via kind. It does not, however, differentiate itself from siblings like pirsch_get_visitors_time_series or pirsch_get_totals, so 4 rather than 5.

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 explicit guidance on when to use this tool versus alternatives. The session/page split is described but framed as a data definition rather than a decision rule, and no exclusions or alternatives are named.

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