Skip to main content
Glama
verygoodplugins

Pirsch Analytics MCP Server

pirsch_growth

Retrieve growth rates for core analytics metrics over a specified time period to compare performance changes.

Instructions

Get growth rates across core metrics for the selected period

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNo
toNoYYYY-MM-DD
tzNo
tagNo
cityNo
fromNoYYYY-MM-DD
pathNoSupports Pirsch operators like ~contains, !not, and ^does-not-contain
sortNo
eventNo
limitNo
scaleNo
startNoPast seconds for active view
filterNo
offsetNo
searchNoContains search on the primary field, e.g. page path for page endpoints
browserNo
channelNo
countryNo
keywordNoGoogle Search Console keyword filter for keyword page lookups
patternNo
to_timeNoHH:MM (same-day only)
hostnameNo
languageNo
platformNo
referrerNo
utm_termNo
directionNo
domain_idNo
exit_pathNo
from_timeNoHH:MM (same-day only)
entry_pathNo
event_nameNoAlias for event when callers use event_name instead of event
session_idNo
utm_mediumNo
utm_sourceNo
visitor_idNo
path_prefixNoMCP-local path prefix filter for page-style tools, e.g. /tutorials/
utm_contentNo
screen_classNo
utm_campaignNo
include_titleNo
referrer_nameNo
event_meta_keyNo
custom_metric_keyNo
custom_metric_typeNo
include_avg_time_on_pageNo
Behavior2/5

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

No annotations exist, so the description must carry the burden. It only says 'get growth rates' without detailing return format, authentication, rate limits, or non-destructive nature. Thus, minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 9 words, which is concise but inadequate for a tool with 46 parameters and no other documentation. It is under-specified.

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

Completeness1/5

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

Given the tool's complexity (46 parameters, no annotations, no output schema, many siblings), the description is severely incomplete. It does not specify needed parameters, metric details, or calculation methods.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is very low (22%) with 46 parameters, yet the description adds no parameter information. It fails to compensate for the schema's gaps, leaving the agent to guess parameter meanings.

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 growth rates across core metrics for a selected period, using a specific verb and resource. It distinguishes from sibling tools like pirsch_overview or pirsch_visitors, though 'core metrics' could be more explicit.

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 such as pirsch_overview or pirsch_compare. The description does not indicate scenarios where growth rates are needed or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/verygoodplugins/mcp-pirsch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server