Privatrak

Find flow nodes

find_flow_nodes

Read-onlyIdempotent

Search the pages and feature events that appear in user paths, with how often each occurs. Returns each node's key, which is what get_flow takes as root or path. 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

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": "find_flow_nodes"
  }
}

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'.
`level`	No	steps (default) or pages; must match the level you pass to get_flow.
`limit`	No	Nodes to return, 1-100. Default 20.
`offset`	No	Nodes to skip, for paging.
`search`	No	Case-insensitive text matched against event type, origin, path and 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).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), lowering the bar. The description still adds real context beyond them: the return shape (each node's key and how often it occurs), the date-format/timezone semantics, and the default window behavior.

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?

Four tight sentences, front-loaded with purpose followed by the return/key contract and date semantics. Every sentence earns its place, though the date-format notes partially overlap with the schema's own from/to descriptions.

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 search tool with 7 fully-documented params and annotations covering safety, the description is nearly complete. Since no output schema exists, it usefully explains what is returned (node keys and occurrence counts), leaving only explicit usage routing to siblings unaddressed.

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 baseline is 3, but the description genuinely adds meaning the schema lacks: dates are interpreted as the project's calendar days (timezone via get_project) while timestamps are UTC, and it explains the default when from/to are omitted. It clarifies the temporal contract rather than repeating the 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 (search) and resource (pages and feature events appearing in user paths) plus the added dimension of frequency. It also positions itself relative to sibling get_flow by noting it returns the node 'key' that get_flow consumes as root/path, so an agent can distinguish its role without opening another schema.

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?

Usage is only implied: the mention that keys feed get_flow signals this is the discovery step before building a flow. It gives useful default-range guidance ('Omit from/to for the last 28 complete days') but never explicitly states when to choose this over siblings like list_pages, list_elements, or get_funnel.

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?