Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Property values

list_property_values
Read-onlyIdempotent

The values a property has taken in a date range, e.g. the page paths or feature names that occurred -- for building exact filters for run_insights_query. Dates are the project's calendar days, YYYY-MM-DD (timezone: get_project); timestamps are UTC. Omit from/to for the last 28 complete days, ending yesterday.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property": "<property>"
    },
    "name": "list_property_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD in the project's timezone, inclusive. Default: yesterday, the last complete day.
fromNoFirst day, YYYY-MM-DD in the project's timezone, inclusive. Default: 27 days before 'to'.
limitNoValues to return, 1-100. Default 20.
matchNoprefix (default) or contains. Use contains for referrer, whose values are full URLs: 'google' finds https://www.google.com/.
searchNoCase-insensitive text the value starts with (or contains, with match=contains).
projectNoProject ID, from list_projects. Required when this connection covers more than one project; may be left out when it covers one (and with an API key, which belongs to one project).
propertyYespage_origin, page_path, page_fragment, referrer, data_track, element_tag, element_selector, element_selector_generalized, automated (always true and false), attrs.KEY or query.PARAM. Not scroll_depth or time_on_page_seconds: they are numbers, with no list of values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / property / description
      Previous value: -"page_origin, page_path, page_fragment, referrer, data_track, element_tag, element_selector, element_selector_generalized, automated (always true and false), attrs.KEY or query.PARAM."New value: +"page_origin, page_path, page_fragment, referrer, data_track, element_tag, element_selector, element_selector_generalized, automated (always true and false), attrs.KEY or query.PARAM. Not scroll_depth or time_on_page_seconds: they are numbers, with no list of values."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered; the description adds real behavioral context the annotations cannot: dates are project calendar days in the project's timezone while timestamps are UTC, and omitting from/to yields the last 28 complete days ending yesterday. It does not describe the return payload (values only, or values plus counts) or ordering, which is the remaining gap.

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 tightly packed sentences: purpose and downstream use first, then date semantics, then the default window. Nothing is redundant at the sentence level, though the opening is a noun phrase rather than a verb phrase, which makes the action slightly less immediate.

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 read-only enumeration tool with a fully described 7-parameter schema and no output schema, the definition covers purpose, date semantics, defaults, and downstream use. The one omission is the shape of the returned values, which an agent cannot infer from any structured field since no output schema exists.

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 parameter, including the enumerable property values and match/search/limit behavior, is already documented. The description restates the from/to default window and date/timezone convention rather than adding syntax or constraints beyond the schema, so it earns the baseline rather than more.

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 states a concrete resource and scope: distinct values a property has taken within a date range, with examples (page paths, feature names) and its downstream purpose (building exact filters for run_insights_query). An agent can distinguish this from list_property_keys (keys, not values) and from run_insights_query (aggregation, not value enumeration) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context — this feeds exact filters into run_insights_query — and states the default window behavior when from/to are omitted, plus the timezone convention. It does not explicitly exclude cases (e.g. when to use list_property_keys instead, or when not to enumerate), but the intended context is unambiguous.

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

All Privatrak 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