Skip to main content
Glama
verygoodplugins

Pirsch Analytics MCP Server

pirsch_entry_pages

Retrieve entry page statistics with filtering, sorting, and optional average time on page to analyze landing page performance.

Instructions

Get entry page stats with sorting, search, and optional average time on page

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 provided. Description implies a read operation but does not disclose pagination, authentication needs, rate limits, or any behavioral traits. The massive parameter list and nested object are not addressed.

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?

Single sentence, concise and front-loaded. However, it could benefit from additional structure given the tool's complexity.

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?

With 46 parameters, no output schema, and no annotations, the description is severely lacking. It omits critical details about output, filtering, and the extensive parameter set, leaving the agent with insufficient guidance.

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 only 22%. The description adds no parameter-level meaning beyond listing a few capabilities; most of the 46 parameters remain undocumented.

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 entry page stats with sorting, search, and optional average time on page. It uses a specific verb and resource, but does not differentiate from sibling tools like pirsch_pages or pirsch_exit_pages.

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 on when to use this tool versus siblings. The description lists capabilities but offers no context for selection.

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