Courier

put_journey_template_locale

Idempotent

Set locale-specific content overrides for a journey-scoped notification template. Each element override must reference an existing element by its id. The template stays a draft; making it live is a separate step this tool cannot perform.

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": {
      "notification_id": "<notification_id>",
      "journey_id": "<journey_id>",
      "locale_id": "<locale_id>",
      "elements": "<elements>"
    },
    "name": "put_journey_template_locale"
  }
}

Input Schema

Name	Required	Description
`state`	No	Template state after update. Must be "DRAFT". These tools cannot publish.
`elements`	Yes	Array of element overrides with id and locale-specific content
`locale_id`	Yes	Locale identifier (e.g. es, fr, pt-BR)
`journey_id`	Yes	The journey template ID that owns this notification. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.
`notification_id`	Yes	The notification 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.

Changed5 schema fields changedSep 22, 2026

changedInput schema / properties / elements / items / properties / id / description

Previous value: -"Target element ID to override"New value: +"Target element ID to override, from a prior get_journey_template or get_journey_template_content response. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."

changedInput schema / properties / journey_id / description

Previous value: -"The journey template ID that owns this notification"New value: +"The journey template ID that owns this notification. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."

changedInput schema / properties / notification_id / description

Previous value: -"The notification template ID"New value: +"The notification template ID. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."

changedInput schema / properties / state / description

Previous value: -"Template state after update"New value: +"Template state after update. Must be \"DRAFT\". These tools cannot publish."

changedInput schema / properties / state / enum

Previous value: -[
-  "DRAFT",
-  "PUBLISHED"
-]New value: +[
+  "DRAFT"
+]

AddedJul 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond these annotations: the template remains a draft, the tool cannot publish, and element overrides must reference existing element ids. This meaningfully supplements the annotation-only safety profile.

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 two sentences with no wasted words. The primary action is front-loaded, and the second sentence adds only high-value constraints about draft state and element id validity.

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?

Given the rich schemas and annotations, the description is largely complete for calling the tool correctly. It explains the draft-state limitation and the referential integrity requirement. It does not explicitly describe overwrite/merge semantics or return behavior, but the idempotentHint and absence of an output schema keep this from being a serious gap.

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 the schema already documents all parameters. The description reinforces that elements are locale-specific overrides and must reference existing ids, but it does not add substantial new parameter semantics beyond what the schema already states. Baseline 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 uses a specific verb and resource: "Set locale-specific content overrides for a journey-scoped notification template." This clearly differentiates it from siblings like put_journey_template_content and put_notification_locale by highlighting both "locale-specific" and "journey-scoped."

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?

The description provides clear context: it operates on a journey-scoped notification template and requires element overrides to reference existing element ids. It also gives an explicit exclusion—"making it live is a separate step this tool cannot perform"—which prevents misuse. It does not name alternative sibling tools, so it falls short of a 5.

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

All Courier tools Inspect

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.