Skip to main content
Glama

Extralingo

by com.extralingo
OverviewDiscussionsAdmin

save_trip

Create or update a server-side trip draft. Returns trip_id, url, trip_url, and continue_url (/s/{id}) so the student can restore selections on Extralingo.com. Not a booking. Requires OAuth trips scope (Bearer token).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoOptional student email for anonymous drafts. With OAuth, the verified account email is used.
localeNoResponse language and site context. One of en, nl, da, sv.
trip_idNoOmit to create a new trip. Pass an existing trip_id from save_trip to update the same continue_url.
school_idNoCraft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID.
configurationNoSame shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoLegacy alias of continue_url.
noteNo
successYes
summaryNo
trip_idNo
trip_urlNo
continue_urlNoShareable Extralingo URL that restores configuration.
configurationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / configuration / additionalProperties
      Added value: +true
    • addedInput schema / properties / configuration / description
      Added value: +"Same shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras."
    • addedInput schema / properties / configuration / properties
      Added value: +{
+  "accommodationGroupId": {
+    "description": "Accommodation group id from list_accommodations (optional).",
+    "type": "string"
+  },
+  "mealType": {
+    "description": "Meal plan key when accommodation is selected.",
+    "type": "string"
+  },
+  "startDate": {
+    "description": "Course start calendar date (YYYY-MM-DD). Typically a Monday from list_starting_dates.",
+    "examples": [
+      "2026-09-07"
+    ],
+    "type": "string"
+  },
+  "students": {
+    "description": "One object per traveller. courseId comes from list_courses.",
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "courseId": {
+          "description": "Course product id from list_courses for this school.",
+          "type": "string"
+        },
+        "weeks": {
+          "description": "Course duration in weeks.",
+          "minimum": 1,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / email / description
      Added value: +"Optional student email for anonymous drafts. With OAuth, the verified account email is used."
    • addedInput schema / properties / locale / description
      Added value: +"Response language and site context. One of en, nl, da, sv."
    • addedInput schema / properties / locale / examples
      Added value: +[
+  "en",
+  "nl",
+  "da",
+  "sv"
+]
    • addedInput schema / properties / school_id / description
      Added value: +"Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID."
    • addedInput schema / properties / school_id / examples
      Added value: +[
+  12345
+]
    • changedInput schema / properties / trip_id / description
      Previous value: -"Omit to create. Pass to update the same URL."New value: +"Omit to create a new trip. Pass an existing trip_id from save_trip to update the same continue_url."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "configuration": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "continue_url": {
+      "description": "Shareable Extralingo URL that restores configuration.",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "success": {
+      "const": true
+    },
+    "summary": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "trip_id": {
+      "type": "string"
+    },
+    "trip_url": {
+      "type": "string"
+    },
+    "url": {
+      "description": "Legacy alias of continue_url.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond annotations: it is a server-side draft (idempotentHint=false in annotations aligns with 'omit trip_id to create a new trip'), it discloses the required OAuth trips scope (Bearer token), and clarifies that anonymous email drafts are possible. Minor gap: it does not state that repeated calls without trip_id create new drafts rather than dedupe.

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?

Three tight sentences, heavily front-loaded: purpose first, output second, constraint/auth last. Every clause carries information an agent needs and nothing is redundant.

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?

For a nested, 5-parameter mutation tool with an output schema, the description covers the essentials: purpose, create/update semantics, auth scope, and non-booking status. Return values are also enumerated even though the output schema already covers them.

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 email, locale, trip_id, school_id, and the configuration object in detail. The description restates only the high-level shape and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource ('Create or update a server-side trip draft') and immediately scopes it against the obvious sibling by declaring 'Not a booking', which separates it from create_booking. The return payload and restore URL are named, so the agent knows exactly what this produces.

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 clear context: create vs update is signaled, and 'Not a booking' rules out create_booking. However it never explicitly names create_booking, get_trip, or email_trip as the alternatives for their respective intents, so routing is implied rather than spelled out.

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

All Extralingo 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