Skip to main content
Glama
verygoodplugins

Pirsch Analytics MCP Server

pirsch_event_pages

Find all pages where a specified event fired, using filter.event to identify the event and optional parameters like date range or path to narrow results.

Instructions

Get pages on which a specific event fired. Requires filter.event

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 are provided, and the description only notes the requirement for filter.event. It does not disclose read-only nature, rate limits, pagination, or output format, leaving significant behavioral gaps.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it omits essential information to the point of under-specification. It is not well-structured for an agent to use effectively.

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 46 parameters, no output schema, and many sibling tools, the description is severely incomplete. It lacks parameter guidance, behavioral details, and usage context, making it inadequate for an AI agent.

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?

With schema description coverage at only 22%, the description adds no meaning beyond 'Requires filter.event', failing to explain the event parameter or any other of the 46 parameters.

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

Purpose5/5

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

The description clearly states 'Get pages on which a specific event fired' with a specific verb and resource, and distinguishes from siblings like pirsch_events or pirsch_pages by focusing on event-triggered pages.

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?

The description mentions 'Requires filter.event' as a prerequisite, but does not provide guidance on when to use this tool versus alternatives like pirsch_events or pirsch_pages, nor when not to use it.

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