Skip to main content
Glama

Pirsch Analytics MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List conversion goals

pirsch_list_goals
Read-only

Conversion goals with their definition (page pattern, event, targets) and the visitors, views and conversion rate for the period. GET /api/v1/statistics/goals.

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

B3.2/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 by structured data. The description adds the return shape (definition fields plus visitors/views/conversion rate), which is genuinely useful, but says nothing about auth requirements, pagination, or rate limits.

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?

Two compact sentences that front-load the returned data and end with the endpoint path. No filler or redundancy, though the raw 'GET /api/v1/statistics/goals' fragment adds little for an agent choosing a tool.

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 nested objects, the description is only adequate. It helpfully describes the returned metrics in lieu of an output schema, but omits required-parameter expectations, pagination behavior, and filter semantics that an agent would need for correct invocation.

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 every one of the 33 parameters is documented in the schema itself. The description adds no parameter-level detail (e.g., required domain_id/from/to, filter syntax), so the baseline of 3 applies.

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 identifies a specific resource (conversion goals) and enumerates what it contains: the definition (page pattern, event, targets) plus visitors, views and conversion rate. The 'list' verb is implied rather than stated, but the resource is unique and no sibling overlaps, so an agent can pick it out.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The only usage signal is implicit (it returns per-period statistics, so a date range is expected), leaving routing entirely to inference.

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