Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Funnels

list_funnels
Read-onlyIdempotent

The project's saved funnels with step counts, trait_scope (how each counts when read for one trait: visitor or step, see get_funnel), is_goal (a goal: its conversions per source and campaign are in list_sources and list_campaigns with goal = its id) and goal_value (what a conversion is worth, in get_project's currency; shown while it is a goal), and each one's entering and completing visitors and conversion over counts_period: the 31 days up to and including today, NOT the 28 complete days the other tools default to. Use it to pick funnels, never to quote or compare numbers; call get_funnel for comparable per-step counts.

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_funnels"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
limitNoItems per page, 1-100. Default 50.
searchNoCase-insensitive substring of the name.
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 only declare readOnly/idempotent/closed-world; the description goes well beyond them by disclosing the non-standard aggregation window ('the 31 days up to and including today, NOT the 28 complete days the other tools default to') and by explaining semantics of trait_scope, is_goal, and goal_value including the currency source. That window mismatch is exactly the kind of trap that produces wrong comparisons if undisclosed.

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 sentences, both front-loaded on the constraint that matters (row contents then the time-window warning), with no filler. Structure suffers slightly from piling trait_scope, is_goal, goal_value, and visitor counts into one deeply nested sentence, which slows parsing.

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?

For a read-only list tool with no output schema, it covers the field semantics, the cross-tool references needed to resolve ids (get_project, list_sources, list_campaigns, get_funnel), and the non-default date window. An agent could select and interpret this tool correctly without opening any sibling.

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 page, limit, search, and project are already documented, and the description adds no syntax or formatting detail about them. Baseline 3 applies; parameter explanation is entirely delegated to 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 the specific verb and resource ('The project's saved funnels') and enumerates exactly what each row carries: step counts, trait_scope, is_goal, goal_value, and entering/completing visitors plus conversion over counts_period. It explicitly distinguishes itself from get_funnel ('see get_funnel') and cross-references list_sources/list_campaigns for goal conversions.

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

Usage Guidelines5/5

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

Gives an explicit use case ('Use it to pick funnels') and an explicit exclusion ('never to quote or compare numbers'), then names the correct alternative with the condition that selects it ('call get_funnel for comparable per-step counts'). Nothing is left to inference.

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