JobMojito

Update coaching catalogue directory

update_catalogue_directory

DestructiveIdempotent

[Coaching catalogue] Update a coaching catalogue directory: rename it, change which sessions it lists (tags_interview_set_filter), re-order its sub-directories (tags_sub), or author its custom Markdown page (content_md). Only the fields you send are changed. Coaching-platform feature.

Updates a directory (page) of the coaching portal catalogue. Only the fields present in the request body are written — everything else keeps its current value, and sending null clears a nullable field. Use it to rename a directory, re-point which sessions it lists (tags_interview_set_filter), re-order or replace its sub-directories (tags_sub), or author its custom Markdown page (content_md).

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Id of the directory to update (the catalogue URL segment). The id itself cannot be changed — create a new directory instead.
`name`	No	Display name of the directory.
`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 the custom directory page. Sending null removes the custom page and restores the default grid; sending a string replaces the whole page. Directives, each ALONE on its own line: `[plan-progress]`, `[directory:<tag-id>]`, `[session:<interview-id>]`, `[sessions]`, `[sessions:<term>]`, `[sessions:filter=<term>,limit=<n>]`. Chips, callouts, cards, columns and buttons are available too — formatting guide: https://developer.jobmojito.com/cookbooks/format-content-with-markdown
`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.
`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. null clears it.
`mojito_language_code`	No	Language of the directory (one of the platform-languages.json codes). The catalogue groups directories by language.
`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 updated directory.
`catalogue_url`	Yes	Public URL of the directory page, when the merchant has a coaching-portal domain configured. Null otherwise.
`updated_fields`	Yes	Names of the fields that were written.
`_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 the custom directory page. Sending null removes the custom page and restores the default grid; sending a string replaces the whole page. Directives, each ALONE on its own line: `[plan-progress]`, `[directory:<tag-id>]`, `[session:<interview-id>]`, `[sessions]`, `[sessions:<term>]`, `[sessions:filter=<term>,limit=<n>]`."New value: +"Markdown for the custom directory page. Sending null removes the custom page and restores the default grid; sending a string replaces the whole page. Directives, each ALONE on its own line: `[plan-progress]`, `[directory:<tag-id>]`, `[session:<interview-id>]`, `[sessions]`, `[sessions:<term>]`, `[sessions:filter=<term>,limit=<n>]`. Chips, callouts, cards, columns and buttons are available too — formatting guide: 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.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description adds real behavioral value beyond that: partial-update semantics ('only the fields present in the request body are written') and the null-clears-a-field rule ('sending null removes the custom page'). It does not expand on the destructive profile (e.g. that replacing tags_sub drops the whole previous list is only in the schema), which keeps it at a solid 4.

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

Conciseness3/5

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

It is front-loaded with the tool name and operations, but the two paragraphs are largely redundant: 'Only the fields you send are changed' and 'Only the fields present in the request body are written' say the same thing, and the four supported operations are listed twice. The duplication costs it a point.

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?

With an output schema present, return values need no explanation, and the annotations carry the safety profile. The description covers the partial-update contract and the main editable fields, leaving only minor gaps (destructive scope of list replacements is schema-only), so it is nearly complete for a 12-param mutation.

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 all 12 parameters thoroughly, including enums and examples. The description restates a few field meanings (tags_interview_set_filter, tags_sub, content_md) but adds no syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb (update) and resource (coaching catalogue directory) and enumerates the concrete operations: rename, re-point session listings, re-order sub-directories, author the Markdown page. Purpose is unambiguous, though it never names its create/get siblings, so differentiation is left to the tool name rather than the prose.

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?

The description implies when to reach for it by listing the field-level operations it supports, but offers no explicit when-to-use/when-not guidance and never names an alternative (e.g. create_catalogue_directory for a new id). Usage is inferable rather than stated.

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.