Skip to main content
Glama

Pirsch Analytics MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List countries, regions, cities and languages

pirsch_list_geography
Read-only

Visitors per country, region, city or language. Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/country, /region, /city or /language.

Input Schema

NameRequiredDescriptionDefault
osNoOperating system. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
toYesLast day, yyyy-mm-dd, whole day included.
tzNoIANA time zone such as Europe/Berlin. Default: the dashboard's time zone.
tagNoTag key to filter for.
cityNoCity name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
fromYesFirst day, yyyy-mm-dd (in the dashboard time zone unless tz is set).
pathNoPage path, for example /pricing. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
sortNoField to sort by, for example visitors, views, sessions or bounce_rate.
tagsNoTag key/value pairs; only results with all pairs match.
eventNoEvent name. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
limitNoResults per page, 1-100 (default 25).
offsetNoResults to skip (default 0). Pass the previous reply's next_offset.
searchNoOnly rows whose main field contains this text.
browserNoBrowser. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
channelNoTraffic channel such as "Paid Search" or "Organic Search". Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
countryNoISO 3166 alpha-2 country code such as jp. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
patternNoRegular expression that filters and groups pages, for example (?i)^/blog/[^/]+$.
hostnameNoHostname (useful for rollup views). Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
languageNoISO 639-1 language code such as en. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
platformNoPlatform.
referrerNoReferrer, usually a URL. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_termNoUTM term. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
dimensionYesWhich breakdown.
directionNoSort direction.
domain_idYesPirsch domain (dashboard) id. Get it from pirsch_list_domains.
exit_pathNoExit page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
entry_pathNoEntry page path. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
event_metaNoEvent metadata key/value pairs; only events with all pairs match.
utm_mediumNoUTM medium. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_sourceNoUTM source. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_contentNoUTM content. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
screen_classNoScreen class XXL, XL, L, M or S. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
utm_campaignNoUTM campaign. Optional filter. A value may start with ! (is not), ~ (contains) or ^ (does not contain).
referrer_nameNoReferrer 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.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the shape of each returned row (visitors, views, sessions, bounces, relative shares) and the four backing endpoints, which matters since there is no output schema.

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 compact sentences, front-loaded with what the tool returns. Every sentence carries information; the endpoint trailer is slightly operational but nonetheless informative, and nothing is padded.

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

Completeness4/5

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

For a 34-parameter aggregation tool with no output schema, the description usefully compensates by naming the returned metrics and confirming the dimension-driven breakdown. It omits mention of pagination/next_offset behavior, which is the one gap an agent might care about.

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%, so the schema already documents all 34 parameters including the !, ~, ^ filter prefixes. The description's country=de and path=~blog examples merely illustrate what the schema already spells out, so it does not materially exceed the baseline.

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?

States a specific resource breakdown ('Visitors per country, region, city or language') that maps directly to the dimension enum, and the endpoint list confirms it is a statistics read. An agent can tell it apart from pirsch_get_platforms, pirsch_list_pages, and pirsch_list_utm purely from the stated dimensions.

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?

Provides illustrative filter usage (country=de, path=~blog) which implies the tool is a filtered aggregation query, but never states when to pick it over siblings or any exclusions. Usage is inferable from the dimension parameter rather than articulated.

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 toolsInspect
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.

Resources