Skip to main content
Glama

Rename a journey

rename_journey
Idempotent

Rename a journey. Nothing it sends changes.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
journey_idYesThe journey, by id from list_journeys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

'Nothing it sends changes' adds real context beyond the annotations: it reassures the agent that renaming does not alter the journey's outbound messages or automation behavior, which the hints (readOnlyHint=false, idempotentHint=true, destructiveHint=false) do not state. It still doesn't say whether the rename takes effect immediately or what the response looks like, but with annotations carrying the safety profile this is a useful addition.

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, front-loaded with the action and immediately followed by the one non-obvious behavioral fact. No filler; it errs only on the side of being extremely terse.

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?

For a low-complexity rename with full schema coverage and annotations covering safety, the description is adequate but thin. It omits usage routing among the many journey siblings and does not mention the unusual optional user_goal parameter or error behavior for invalid journey ids.

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 all four parameters (site_id, journey_id, name, user_goal) are documented in the schema. The description adds no additional meaning, such as name constraints or uniqueness behavior, so 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?

Specific verb+resource ('Rename a journey') that maps exactly to the name, so intent is unambiguous. It doesn't distinguish itself from adjacent journey tools (get_journey, set_journey_enabled, draft_journey, delete_journey) or from rename_page/rename_site, but the verb+resource pairing is clear.

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 statement of when to use this versus set_journey_enabled, draft_journey, or update_journey_step, and no prerequisites such as needing a journey_id from list_journeys. Usage is only inferable from the tool name itself.

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