Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Check funnel steps

preview_funnel
Read-onlyIdempotent

Check draft funnel steps before create_funnel; saves nothing. Per step, how many events it matched in the range, matched exactly as a saved funnel matches them. Events, not visitors, and no conversion: past conversion cannot be computed for steps that were not a funnel then. A step with 0 matched_events would count nobody: fix page_path (exact, as stored, e.g. /products/:id; see list_property_values; for many pages use a feature rule with starts_with or matches and step on its feature) or the feature name, unless it is a data-track name that is not deployed yet. At most 92 days per call. 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": {
      "steps": "<steps>"
    },
    "name": "preview_funnel"
  }
}

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'. At most 92 days in one call.
stepsYesDraft steps exactly as for create_funnel: 2 to 10, each with filters (event_type, page_origin, page_path, feature).
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, and the description reinforces this with 'saves nothing'. It goes well beyond annotations by disclosing the 92-day per-call cap, that matching mirrors saved-funnel semantics, that it counts events not visitors, that no conversion is returned, and the timezone/date conventions.

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?

It is a dense single block, but it is front-loaded with the purpose and the most decision-relevant facts (saves nothing, events not visitors, no conversion) before the operational detail. The length is justified by the number of constraints, though a break into a short 'returns' line would tighten it further.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so: 'Per step, how many events it matched in the range'. Combined with the date defaults, the 92-day limit, and the failure-mode guidance, an agent has everything needed to call it correctly.

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 the schema already documents the four parameters, giving a baseline of 3. The description adds real meaning beyond that: it explains what page_path must be (exact, as stored, e.g. /products/:id), points to list_property_values, and prescribes a feature-rule workaround (starts_with/matches) for multi-page steps.

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 opening clause gives a specific verb+resource ('Check draft funnel steps') and immediately distinguishes the tool from its natural sibling by stating it is a dry run before create_funnel that 'saves nothing'. An agent can tell this apart from get_funnel (reads a saved funnel) without opening either 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 explicitly scopes the tool to use 'before create_funnel' and gives a concrete troubleshooting path for the failure case (a step with 0 matched_events). It does not, however, name a when-not-to-use condition or explicitly contrast with get_funnel/get_funnel_trend among the siblings.

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