Skip to main content
Glama
Sign In

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

list_journey_versions

Read-only

List published versions of a journey, ordered most recent first.

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": {
      "journey_id": "<journey_id>"
    },
    "name": "list_journey_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
journey_idYesThe journey template ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already mark the operation as read-only, and the description adds useful behavioral context: only published versions are included and they are ordered newest first. It does not mention pagination or output shape, but for a simple read-only version list that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence contains the operation, resource, filter, and ordering with zero filler. The most important scoping information is at the front.

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 one-parameter, read-only listing tool, the description covers what is listed and the order. It is slightly incomplete because it does not describe the returned version objects or mention pagination, and the journey-versus-template terminology is not reconciled.

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% and the single parameter is already documented as 'The journey template ID', so the description does not need to add much. It adds little beyond the schema and slightly mixes terminology by calling the resource a journey rather than a journey template.

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?

The description names a specific operation (list), a resource (published versions of a journey), and an ordering (most recent first), so a caller knows what to expect. It does not explicitly differentiate this from the closely named sibling list_journey_template_versions, so it misses the top score.

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?

No guidance is given about when to use this tool versus siblings such as list_journey_template_versions or get_journey. The word 'published' implies a scope restriction, but no alternative or exclusion is stated explicitly.

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

All Courier 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