Pirsch Analytics MCP by usefulapi

List hostnames

pirsch_list_hostnames

Read-only

Traffic per hostname. Mostly useful for rollup views that combine several hostnames. GET /api/v1/statistics/hostname.

Input Schema

Name	Required	Description
`os`	No	Operating system. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`to`	Yes	Last day, yyyy-mm-dd, whole day included.
`tz`	No	IANA time zone such as Europe/Berlin. Default: the dashboard's time zone.
`tag`	No	Tag key to filter for.
`city`	No	City name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`from`	Yes	First day, yyyy-mm-dd (in the dashboard time zone unless tz is set).
`path`	No	Page path, for example /pricing. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`sort`	No	Field to sort by, for example visitors, views, sessions or bounce_rate.
`tags`	No	Tag key/value pairs; only results with all pairs match.
`event`	No	Event name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`limit`	No	Results per page, 1-100 (default 25).
`offset`	No	Results to skip (default 0). Pass the previous reply's next_offset.
`search`	No	Only rows whose main field contains this text.
`browser`	No	Browser. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`channel`	No	Traffic channel such as "Paid Search" or "Organic Search". Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`country`	No	ISO 3166 alpha-2 country code such as jp. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`pattern`	No	Regular expression that filters and groups pages, for example (?i)^/blog/[^/]+$.
`hostname`	No	Hostname (useful for rollup views). Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`language`	No	ISO 639-1 language code such as en. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`platform`	No	Platform.
`referrer`	No	Referrer, usually a URL. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`utm_term`	No	UTM term. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`direction`	No	Sort direction.
`domain_id`	Yes	Pirsch domain (dashboard) id. Get it from pirsch_list_domains.
`exit_path`	No	Exit page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`entry_path`	No	Entry page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`event_meta`	No	Event metadata key/value pairs; only events with all pairs match.
`utm_medium`	No	UTM medium. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`utm_source`	No	UTM source. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`utm_content`	No	UTM content. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`screen_class`	No	Screen class XXL, XL, L, M or S. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`utm_campaign`	No	UTM campaign. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
`referrer_name`	No	Referrer name, usually the hostname. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that this is a GET statistics endpoint returning aggregated traffic, but says nothing about pagination, result shape, or row limits beyond what the schema states.

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?

Three short sentences, front-loaded with the purpose before the usage hint. The raw endpoint path ('GET /api/v1/statistics/hostname') is of marginal value to an agent and is the only near-wasteful element.

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

Completeness3/5

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

With 33 parameters, no output schema, and annotations covering only safety, the description is adequate but thin: it never characterizes the returned rows or pagination behavior, which the agent needs for a list/statistics tool. The rich schema compensates for the parameter side, keeping this at minimum viable.

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

Parameters3/5

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

Schema description coverage is 100% across all 33 parameters, so the schema fully carries parameter meaning. The description adds no filter semantics, defaults, or syntax guidance beyond that baseline.

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 states a specific resource and metric: 'Traffic per hostname', which tells the agent this returns an aggregated hostname breakdown rather than raw events. It is clear on its own but does not name any sibling (e.g., pirsch_list_referrers or pirsch_list_pages) to anchor differentiation among the many near-identical list tools.

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?

'Mostly useful for rollup views that combine several hostnames' gives a real when-to-use scenario, which is more than most siblings offer. However, it provides no exclusions and no pointer to alternative list endpoints, so an agent choosing among the ~27 list tools still has to infer the rest.

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

All Pirsch Analytics MCP by usefulapi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List hostnames

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources