Skip to main content
Glama

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

list_journey_templates

Read-only

List notification templates scoped to a journey. Journey-scoped templates can only be used by send nodes within the same journey. Call this to discover template IDs before wiring send nodes in replace_journey.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (1–100)
cursorNoCheck the response's paging.more before calling again — false means every template already came back, and calling 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.
journey_idYesThe journey template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"Check the response's paging.more before calling again — false means every template already came back, and calling 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 / journey_id / description
      Previous value: -"The journey template ID"New value: +"The journey template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."
  2. Added

TDQS

A4/5.0
Behavior3/5

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

The annotation includes readOnlyHint=true, so the safety profile is already known. The description adds useful context about journey scoping and the template-ID discovery purpose, but it does not disclose additional behavioral details such as result ordering, default page size, or overall response structure. This is acceptable for a read-only list tool but not especially rich.

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?

Two sentences with no filler. The primary purpose and scope appear first, followed by a single actionable usage hint. Every clause earns its place.

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 simple read-only listing tool, the description is sufficient: it states the object type, scope, and the workflow context. The schema handles parameter details, including paging semantics. There is no output schema, but the description's focus on discovering template IDs aligns with what the agent needs before calling replace_journey.

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 detailed parameter descriptions for journey_id, limit, and cursor, including the instruction to pass cursor back byte-for-byte. The description itself does not add parameter-level meaning, 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.

Purpose5/5

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

The description starts with a specific verb-resource pair, 'List notification templates scoped to a journey,' which precisely states both the object type and the scope. It further clarifies that journey-scoped templates are distinct and usable only by send nodes within the same journey, distinguishing this tool from broader template-listing siblings.

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

Usage Guidelines4/5

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

It gives a clear use case: 'Call this to discover template IDs before wiring send nodes in replace_journey.' This tells the agent when to invoke the tool and why. It does not explicitly name alternatives or exclusion cases, but the journey scoping provides enough context to avoid confusion with tenant-level template tools.

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