JobMojito

Create coaching catalogue directory

create_catalogue_directory

Destructive

[Coaching catalogue] Create a directory (page) in the coaching portal catalogue. A directory nests other directories (tags_sub), lists coaching sessions whose own tags match its tags_interview_set_filter, and can carry a fully custom Markdown page (content_md) with [sessions], [directory:…], [session:…] and [plan-progress] directives. Coaching-platform feature.

Creates a directory (page) in the coaching portal catalogue. A directory nests other directories through tags_sub, lists coaching sessions through tags_interview_set_filter, and can replace the default grid with a custom Markdown page through content_md. The id you choose is the catalogue URL segment and cannot be changed afterwards.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Directory id — also the catalogue URL segment (/catalogue/<id>) and the value other directories reference in their `tags_sub`. Lowercase letters, digits and single - or _ separators. Convention is to end language-specific directories with the language code, e.g. `sales-coaching-en`.
`name`	Yes	Display name of the directory, shown as the page title and on its card.
`status`	No	Lifecycle status of the catalogue directory. Options — `draft`: Not published — the directory exists but is not served to visitors. \| `active`: Published and served in the catalogue. \| `archived`: Retired — kept for reference but no longer served..
`tags_sub`	No	Ids of the directories nested under this one, in display order. Replaces the whole list — send the full set, not just the additions. A referenced directory only appears if it exists and is visible to the viewer.
`coach_plan`	No	Coaching-plan stage this item belongs to, used by the coaching-plan progress view. Omit/null to leave it out of any plan. Options — `demo`: Demo session. \| `screening`: Screening-interview practice. \| `2nd`: Second-interview practice. \| `3rd`: Third-interview practice. \| `closing`: Closing / salary-negotiation practice. \| `job-specific`: Job-specific coaching. \| `other`: Anything that does not fit the other buckets..
`content_md`	No	Markdown for a custom directory page. When set (even as an empty string) the markdown replaces the default grid and decides the layout itself; null renders the plain grid of sub-directories and sessions. Alongside normal Markdown you can place these directives, each ALONE on its own line: `[plan-progress]` (the learner's coaching-plan progress), `[directory:<tag-id>]` (a card for one sub-directory), `[session:<interview-id>]` (a card for one session), `[sessions]` (every session in this directory), `[sessions:<term>]` (sessions matching a term), `[sessions:filter=<term>,limit=<n>]` (a filtered, capped list). A directive on a line with other text is rendered as ordinary text. Chips, callouts, cards, columns and buttons are available here too — full vocabulary: https://developer.jobmojito.com/cookbooks/format-content-with-markdown
`parent_tag`	No	Id of an existing directory to nest this new one under: the new id is appended to that directory's `tags_sub`. Omit to create a top-level directory (reachable via a direct link, or by adding it to another directory later).
`visibility`	No	Who can see the catalogue directory. Options — `public`: Shared across every merchant. Platform admins only — a merchant caller is rejected by row-level security. \| `merchant_public`: Listed in the merchant's own catalogue — the normal choice. \| `merchant_invite`: Owned by the merchant but not listed; reachable only for invited users. \| `merchant_unlisted`: Owned by the merchant but not listed; reachable only via a direct link..
`description`	No	Short description shown on the directory card.
`merchant_id`	No	Merchant that owns the directory. Admin / sub-merchant callers only; otherwise taken from your token.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
`cover_image_url`	No	Cover image URL shown on the directory card.
`mojito_language_code`	No	Language of the directory (one of the platform-languages.json codes). The catalogue groups directories by language; defaults to `en` when omitted.
`tags_interview_set_filter`	No	Tag filter selecting which coaching sessions this directory lists: a session appears when its own `tags` contain EVERY tag here (an AND, not an OR). Only `active` coaching/persona sessions with visibility `public` or `merchant_public` are listed. Set the matching tags on the session with the create-interview / job-interview-update `tags` field.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Id of the created directory.
`parent_tag`	Yes	The directory this one was nested under, when `parent_tag` was supplied.
`merchant_id`	Yes	Owning merchant id. Null for a platform-wide (`public`) directory.
`catalogue_url`	Yes	Public URL of the directory page, when the merchant has a coaching-portal domain configured. Null otherwise.
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / conversation_id / description

Previous value: -"Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it."New value: +"Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedOutput schema / properties / _mcp_instructions

Added value: +{
+  "description": "Server-issued metadata for this conversation.",
+  "properties": {
+    "conversation_id": {
+      "description": "The server-issued conversation identifier.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedAug 24, 2026

changedInput schema / properties / content_md / description

Previous value: -"Markdown for a custom directory page. When set (even as an empty string) the markdown replaces the default grid and decides the layout itself; null renders the plain grid of sub-directories and sessions. Alongside normal Markdown you can place these directives, each ALONE on its own line: `[plan-progress]` (the learner's coaching-plan progress), `[directory:<tag-id>]` (a card for one sub-directory), `[session:<interview-id>]` (a card for one session), `[sessions]` (every session in this directory), `[sessions:<term>]` (sessions matching a term), `[sessions:filter=<term>,limit=<n>]` (a filtered, capped list). A directive on a line with other text is rendered as ordinary text."New value: +"Markdown for a custom directory page. When set (even as an empty string) the markdown replaces the default grid and decides the layout itself; null renders the plain grid of sub-directories and sessions. Alongside normal Markdown you can place these directives, each ALONE on its own line: `[plan-progress]` (the learner's coaching-plan progress), `[directory:<tag-id>]` (a card for one sub-directory), `[session:<interview-id>]` (a card for one session), `[sessions]` (every session in this directory), `[sessions:<term>]` (sessions matching a term), `[sessions:filter=<term>,limit=<n>]` (a filtered, capped list). A directive on a line with other text is rendered as ordinary text. Chips, callouts, cards, columns and buttons are available here too — full vocabulary: https://developer.jobmojito.com/cookbooks/format-content-with-markdown"

changedInput schema / properties / content_md / example

Previous value: -"## Sales coaching\n\nPick a session to practise with.\n\n[sessions:filter=objection-handling,limit=6]\n"New value: +"## Sales coaching\n\nPick a session to practise with.\n\n[chip:6 sessions] [chip:Beginner,tone=accent]\n\n[sessions:filter=objection-handling,limit=6]\n"

AddedAug 7, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare the mutation profile (destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely useful behavior beyond them and beyond the schema: the id becomes an immutable URL segment that 'cannot be changed afterwards', and custom markdown 'replaces' the default grid rather than augmenting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains two near-identical paragraphs: the second ('Creates a directory (page) in the coaching portal catalogue. A directory nests other directories through tags_sub...') is a verbatim paraphrase of the first. Only the trailing 'id is the catalogue URL segment and cannot be changed afterwards' sentence is unique, so a large share of the text is duplicated rather than earning its place.

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?

An output schema exists, so return values need not be described, and the 14-parameter schema is exhaustively documented. The description covers the concept of a directory, its nesting/listing behavior, the markdown page replacement, and the immutability of the id — enough for an agent to call it correctly, with only the not-named update sibling and parent-existence prerequisites left implicit.

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% across all 14 parameters, including enum explanations for status/visibility/coach_plan and detailed semantics for tags_sub, tags_interview_set_filter and content_md. The description restates a few of these roles (tags_sub, tags_interview_set_filter, content_md) but adds no syntax, format or edge-case detail the schema does not already carry, so baseline 3 is correct.

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?

The description states a concrete verb+resource ('Create a directory (page) in the coaching portal catalogue') and clarifies what a directory actually is — a node that nests sub-directories and lists sessions. It never names or contrasts itself with the obvious sibling update_catalogue_directory, so discrimination relies on the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the text explains that directories can be top-level or nested via parent_tag and can be customised via content_md, which hints at when those options apply. But there is no explicit 'use this to...' vs 'use update_catalogue_directory to...' routing, no stated prerequisites (a parent directory must already exist), and no when-not guidance.

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

All JobMojito 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.