Extralingo

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

Name	Required	Description
`email`	No	Optional student email for anonymous drafts. With OAuth, the verified account email is used.
`locale`	No	Response language and site context. One of en, nl, da, sv.
`trip_id`	No	Omit to create a new trip. Pass an existing trip_id from save_trip to update the same continue_url.
`school_id`	No	Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID.
`configuration`	No	Same shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras.

Output Schema

Name	Required	Description
`url`	No	Legacy alias of continue_url.
`note`	No
`success`	Yes
`summary`	No	Human-readable configuration summary for agents.
`trip_id`	No	Shareable trip id (/s/{id}).
`trip_url`	No
`school_id`	No	Craft school entry id.
`school_url`	No
`school_name`	No
`continue_url`	No	Shareable Extralingo URL that restores configuration.
`configuration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 3, 2026
- addedOutput schema / properties / school_id
```
Added value: +{
+  "description": "Craft school entry id.",
+  "type": "integer"
+}
```
- addedOutput schema / properties / school_name
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / school_url
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / summary / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / summary / description
```
Added value: +"Human-readable configuration summary for agents."
```
- changedOutput schema / properties / summary / type
```
Previous value: -"object"New value: +"string"
```
- addedOutput schema / properties / trip_id / description
```
Added value: +"Shareable trip id (/s/{id})."
```

Changed10 schema fields changedOct 3, 2026

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"
+}

First observedOct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the non-readOnly, non-idempotent, non-destructive, closed-world profile, and the description adds real context on top: the required OAuth trips scope (Bearer token) and that anonymous drafts can use an email instead. It does not say whether an update replaces or merges existing selections, which is the main behavioral ambiguity left for an upsert.

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 short sentences, front-loaded with the action, then the return contract, then the auth requirement. Nothing is redundant or padded.

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?

With a full output schema, complete annotations, and 100% schema coverage, the description only needs to supply the auth scope, the non-booking boundary, and the restore-on-Extralingo purpose — all of which it does. Nothing an agent needs to call this correctly is missing.

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% and the parameters are richly documented (school_id provenance, courseId from list_courses, startDate format), so the schema does the heavy lifting. The description adds no parameter-level detail of its own, which is the expected baseline of 3 at full coverage.

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 and resource ('Create or update a server-side trip draft') and immediately scopes it against the obvious sibling with 'Not a booking', so an agent can distinguish it from create_booking and get_trip without opening a schema.

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 the create-vs-update rule via trip_id and an explicit exclusion ('Not a booking'), which routes the agent away from booking tools. It does not, however, name a specific sibling to use instead or state prerequisites beyond the OAuth scope, so it stops short of a full when/when-not/alternative statement.

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

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