Skip to main content
Glama

Customer journeys

journeys
Read-onlyIdempotent

Paginated observed journeys for one website. Filter by first-touch source and medium, lifecycle, sort, page, and limit.

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

Input Schema

NameRequiredDescriptionDefault
toNoinclusive end YYYY-MM-DD; default today
fromNoinclusive start YYYY-MM-DD; default last 60 days
pageNopage number; default 1
sortNonewest, oldest, spent, or stage; default newest
limitNopage size 1-100; default 25
mediumNofirst-touch medium; supply with source
periodNonamed window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month
sourceNofirst-touch source; supply with medium
currencyNolowercase ISO 4217 code
lifecycleNolifecycle_state; same enum as GET /v1/analytics/journeys
time_zoneNoIANA time zone; default UTC
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website
granularityNoday, week, or month; default day

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful facts that results are paginated and based on observed data. It does not explain what 'observed' excludes, how period interacts with from/to, or anything about result volume.

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 short sentences with the resource and scope front-loaded, so it is easy to scan. The second sentence spends space re-listing parameters the schema already documents, which is the main wasted clause.

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 13 optional parameters, an output schema, and full annotation coverage, the description covers the basics but leaves real gaps: granularity's effect on results and the period/from-to precedence are undocumented in prose. Adequate to invoke, thin for a tool of this complexity.

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 every one of the 13 parameters is already documented, including the period-vs-from/to alternative and the source/medium pairing. The description merely repeats a subset (source, medium, lifecycle, sort, page, limit) and adds no meaning beyond the schema; baseline 3 applies.

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

Purpose4/5

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

States a concrete resource and scope: 'paginated observed journeys for one website'. An agent knows this returns a list of journeys scoped to a single site. It stops short of distinguishing itself from the sibling journey_detail, so the agent must infer which one returns the drill-down.

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?

The second sentence is a partial parameter enumeration rather than usage guidance; it never says when to use this list endpoint versus journey_detail, nor does it state prerequisites such as needing a website_id when the account has multiple sites. No when-not guidance is offered.

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