Skip to main content
Glama
verygoodplugins

Pirsch Analytics MCP Server

pirsch_exit_pages

Get exit page statistics for your website, with options to sort, search, and filter by dimensions like path, browser, country, and more.

Instructions

Get exit page stats with sorting and search

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?

With no annotations, the description carries full burden. It does not disclose behavioral traits such as whether the tool requires authentication, how it handles large datasets, or if it returns paginated results. The phrase 'with sorting and search' hints at functionality but lacks detail.

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 sentence, highly concise. It front-loads the core purpose. However, it is too minimal for a complex tool with 46 parameters, sacrificing clarity for brevity.

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 the tool's complexity (46 parameters, no output schema, no annotations), the description is insufficient. It does not explain what 'stats' means, how to interpret results, or which filters are essential. The agent lacks critical context for proper usage.

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

Parameters2/5

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

Schema description coverage is 22%, so the description should compensate. However, it only mentions 'sorting and search' generically, adding no meaning beyond what is in the schema. It does not explain which parameters map to sorting/search or how they work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get exit page stats with sorting and search', which identifies the resource (exit pages) and action (get stats). However, 'stats' is vague and does not distinguish well from sibling tools like pirsch_entry_pages or pirsch_pages. More specificity about what stats (e.g., counts, metrics) would improve clarity.

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 (e.g., pirsch_pages, pirsch_entry_pages). The description does not mention prerequisites, typical use cases, or situations where this tool is preferred.

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