Privatrak

Feature usage

list_features

Read-onlyIdempotent

Features ranked by use (event count) in a date range, paged. compare_previous adds each feature's count in the equally long period before and the change (the biggest movers), plus stopped: features used before with no events now, which the ranking cannot show and which is the clearest sign something broke. Features are only events with a data-track name or matched by a feature rule; untagged clicks are not features. 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. Today is still in progress: a range including it reads as a drop against complete days. A period marked starts_before_data begins before the project has data (see data_from): those days read as zero, not as a quiet period. Quote counts with every percentage; a big change on a small count is noise, not a finding.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_features"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD in the project's timezone, inclusive. Default: yesterday, the last complete day.
`from`	No	First day, YYYY-MM-DD in the project's timezone, inclusive. Default: 27 days before 'to'.
`page`	No	Page number, from 1.
`limit`	No	Features per page, 1-100. Default 50.
`trait`	No	Only count visitors carrying this session trait value.
`search`	No	Case-insensitive substring of the feature name.
`project`	No	Project 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).
`sort_by`	No	total_events (default) or data_track.
`sort_dir`	No	desc (default) or asc.
`compare_previous`	No	Also return each feature's count in the equally long period just before, and the change.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark it read-only/idempotent, but the description adds substantial behavioral context beyond them: the `stopped` semantics for compare_previous, that starts_before_data days read as zero not quiet, and that today is in-progress. This is genuinely useful operational context.

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?

Front-loaded with purpose and dense with useful detail, but the single long run-on block packs many clauses together, making it slightly harder to scan than a cleanly segmented description. Nearly every sentence earns its place.

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 10-param tool with no output schema, the description covers date/timezone semantics, compare_previous additions, and data-completeness caveats well. It leaves the base ranking's return shape somewhat implicit, but the safety and semantics are otherwise thoroughly addressed.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description meaningfully elaborates: it explains the default date window, the intent of compare_previous (prior equal-length period + change + stopped), and cautions on percentage-vs-count interpretation. It adds value over the raw schema.

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 verb+resource+ordering: features ranked by event count in a date range, paged. It even defines what counts as a 'feature' (data-track name or feature rule; untagged clicks excluded), so an agent understands the scope precisely without opening a 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?

Gives clear conditions: when to set compare_previous, when to omit from/to (last 28 complete days), and warns that including today reads as a drop. It lacks explicit routing to a named sibling alternative (e.g. get_feature_timeseries), so not a full 5.

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

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

Resources

Need Help?