Your Next Tours

Reset Trip Join Link

rotate_trip_join_link

Destructive

Reset the trip's open join link and 6-digit join code (draft or active trip). The old link, QR code and code stop working immediately; use it after removing a participant so they cannot rejoin as a guest. Participants are NOT notified: share the returned joinUrl with the group yourself. Params: id (trip uuid).

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": {
      "id": "<id>"
    },
    "name": "rotate_trip_join_link"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`joinUrl`	No
`joinCode`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the destructiveHint/idempotentHint annotations: the old link, QR code and code stop working immediately, each call invalidates prior credentials, participants are not notified, and the agent must share the returned joinUrl itself. This is exactly the operational context annotations cannot convey.

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?

Four short sentences, front-loaded with what changes and the immediate consequence, then the use case, then the notification caveat. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, and the description still names the key return field (joinUrl) and the required follow-up action. For a single-parameter destructive reset, everything an agent needs to call it correctly is present.

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 0%, so the description must carry the burden, and it only restates the parameter as 'id (trip uuid)' — which the schema's uuid format and pattern already establish. It adds minimal meaning (trip vs. other ids) but no format or sourcing guidance.

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?

States a specific verb (reset) and resource (the trip's open join link and 6-digit join code), and scopes it to draft or active trips. An agent can immediately tell this apart from sibling mutation tools like update_trip or remove_trip_participant.

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?

Gives a concrete triggering scenario: use it after removing a participant so they cannot rejoin as a guest. That is clear when-to-use context, but it does not explicitly name the alternative tools or state when not to rotate the link.

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

All Your Next Tours 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.

Resources

Need Help?