Skip to main content
Glama

Tally by Outpost

Path to purchase

get_purchase_paths
Read-onlyIdempotent

How buyers got there: time from first visit to purchase, visits and pages before paying, first-touch to credited-source flows, and the pages buyers saw before paying.

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

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
siteNoThe site's id. Optional: the API key's site is the one read.
limitNoRows at most (default 8).
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. Because there is no output schema, the description's enumeration of what comes back (time from first visit to purchase, pages seen before paying) adds genuine value about the response. It still says nothing about row ordering, default period behavior, or how the four metric groupings are combined in a single response.

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?

A single front-loaded sentence with no filler, organized as a readable list of what the report covers. It is dense but not padded; the only weakness is that the parallel metric clauses blur together without structural markers.

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

Completeness3/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 usefully sketches the return contents, which is the right instinct for a 6-parameter analytics report with nested filters. What is missing is routing guidance among many analytics siblings and any note on default behavior, which leaves an agent guessing at selection.

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 coverage is 100% with per-field descriptions, enum values, and the AND-semantics of the nested filters all documented inline, so the schema does the heavy lifting. The description adds no parameter meaning beyond it — notably nothing about how limit interacts with the four metric groups or how period versus from/to precedence plays out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"How buyers got there" plus four metric groups (time-to-purchase, visits/pages before paying, first-touch vs credited source, pages seen before paying) does convey the report's subject matter. But the sentence is a metric list rather than a stated verb+resource, and it gives no signal for how this differs from siblings like get_funnels, get_breakdown, or get_customer_value, all of which could plausibly cover similar ground.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no when-not-to-use, and no named alternative. An agent must infer from the metric list alone whether this is the right tool versus get_funnels for conversion flow or get_breakdown for attribution splits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources