Skip to main content
Glama
verygoodplugins

Pirsch Analytics MCP Server

pirsch_referrers

Retrieve referrer statistics with optional filters and sorting to analyze traffic sources.

Instructions

Get referrer statistics with filters and sorting

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, so the description carries full burden. It only says 'Get referrer statistics' but omits behavioral traits like read-only nature, pagination details, rate limits, or authentication requirements. For a complex tool with 46 parameters, this is insufficient.

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, front-loaded with the core verb and resource. It is concise with no wasted words. However, it could include slightly more context without sacrificing brevity.

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 output schema, many sibling tools), the description is extremely incomplete. It does not explain return values, how to use the nested 'filter' object, common use cases, or how to interpret results. This leaves the agent with insufficient context to use the tool effectively.

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%, meaning many parameters lack descriptions. The tool description does not add any parameter-specific information or compensate for the low coverage. It merely mentions 'filters and sorting' without explaining common parameters like 'from', 'to', 'filter', or 'sort'.

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 the verb 'Get', the resource 'referrer statistics', and mentions key features 'filters and sorting'. It distinguishes from sibling tools like pirsch_utm, pirsch_overview, etc., which focus on other entities.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., pirsch_utm or pirsch_overview). It does not state prerequisites, use cases, or conditions that favor this tool.

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