Skip to main content
Glama

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

list_journeys

Read-only

List journey templates in the workspace, returning the journey IDs and version state of each. Optionally filter by version (published or draft).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoIf a response has no cursor, every journey already came back — calling this again with the same arguments returns the same page, not new data. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call.
versionNoFilter by version state. Defaults to published, and the two are never combined in one call. If you don't know whether the journey you want is published or still a draft, calling this twice — once per value — is the correct way to check both, not a repeat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"If a response has no cursor, every journey already came back — calling this again with the same arguments returns the same page, not new data. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call."
    • changedInput schema / properties / version / description
      Previous value: -"Filter by version state. Defaults to published."New value: +"Filter by version state. Defaults to published, and the two are never combined in one call. If you don't know whether the journey you want is published or still a draft, calling this twice — once per value — is the correct way to check both, not a repeat."
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=true, the description does not need to establish safety, and it adds useful output context by stating that journey IDs and version state are returned. It does not disclose pagination behavior, but the cursor parameter schema already covers that thoroughly, so the description's contribution is adequate but not substantial.

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?

The description is a single, front-loaded sentence that communicates the resource, scope, output, and optional filter with no wasted words. It is concise without sacrificing the key information an agent needs.

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?

The description explains what is returned (IDs and version state) and the available filter, and the schema covers cursor mechanics and version defaults. It is reasonably complete for a simple list operation, though it could have resolved the ambiguity with sibling list_journey_templates by noting what this tool is not.

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%, and the parameter descriptions for cursor and version are already detailed. The description merely restates the version filter in prose, adding no new semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the verb 'list', the resource 'journey templates in the workspace', and the expected output 'journey IDs and version state'. However, it does not distinguish this tool from the sibling list_journey_templates, which could plausibly serve the same purpose, so it falls short of full differentiation.

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 description implies its purpose but provides no explicit guidance on when to use this tool over alternatives like list_journey_templates, list_journey_versions, or get_journey_template. The 'Optionally filter by version' note addresses parameter usage, not tool selection, so an agent gets little help choosing correctly among the many journey-related siblings.

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