JobMojito

Get coaching catalogue directory

get_catalogue_directory

Read-onlyIdempotent

[Coaching catalogue] Read one catalogue directory in full: its settings, its custom Markdown page (content_md), its resolved sub-directories, and the coaching sessions its tag filter currently matches — which is how you verify that a session's tags actually place it in this directory. Read before updating: content_md, tags_sub and tags_interview_set_filter are replaced wholesale, so you need the current value to extend it.

Reads one catalogue directory in full: its settings, its custom Markdown page (content_md), the sub-directories it nests, and the coaching sessions its tags_interview_set_filter currently matches. Read a directory before updating it — content_md, tags_sub and tags_interview_set_filter are replaced wholesale by catalogue-tag-update, so you need the current value to extend rather than overwrite it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Id of the catalogue directory to read (the catalogue URL segment).
`merchant_id`	No	Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Directory id — also the catalogue URL segment.
`name`	Yes	Display name.
`status`	Yes	Lifecycle status.
`tags_sub`	Yes	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`	Yes	Coaching-plan stage, when the directory belongs to one.
`content_md`	Yes	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
`created_at`	Yes	Creation timestamp (ISO 8601).
`updated_at`	Yes	Last update timestamp (ISO 8601).
`visibility`	Yes	Who can see it.
`description`	Yes	Short description shown on the directory card.
`merchant_id`	Yes	Owning merchant id. Null for a platform-wide directory.
`catalogue_url`	Yes	Public URL of this directory page, when the merchant has a coaching-portal domain configured.
`cover_image_url`	Yes	Cover image URL.
`sub_directories`	Yes	The directories listed in `tags_sub`, resolved and in display order. An id in `tags_sub` that does not resolve (deleted, or not visible to you) is simply absent here — compare the two to spot a broken link.
`matched_sessions`	Yes	The coaching/persona sessions this directory currently lists, applying the same rules as the live portal: `active`, type `coaching` or `persona`, visibility `public` or `merchant_public` for this merchant, and `tags` containing every tag of `tags_interview_set_filter`. Empty when the filter is null. Capped at 200.
`is_start_directory`	Yes	True when this is the directory the merchant's catalogue opens on.
`mojito_language_code`	Yes	Directory language.
`tags_interview_set_filter`	Yes	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.
`matched_sessions_truncated`	Yes	True when more sessions match than the 200 returned — narrow `tags_interview_set_filter` if you see this.

TDQS

A4.2/5.0

Behavior5/5

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

The description goes well beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by disclosing the critical behavior that `content_md`, `tags_sub`, and `tags_interview_set_filter` are replaced wholesale on update, so reading first is necessary to avoid overwriting. It also clarifies that the read returns resolved sub-directories and matched sessions, not just the directory's own metadata. There is no contradiction with the read-only annotations.

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 is noticeably duplicated: the first bracketed paragraph and the following paragraph both state nearly identical information about reading a directory, its returned fields, and the wholesale replacement warning. This wastes space and muddles the front-loading. A single, tight summary would be more concise and easier for an agent to parse.

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?

Given that this is a read-only get operation with an output schema, described parameters, and the full behavioral nuance about update replacement, the description covers everything needed to call the tool correctly. The $merchant_id$ scoping is already documented in the schema. Any redundancy in the description does not cause content to be omitted.

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?

The schema already has 100% parameter coverage, including examples and permission notes for `merchant_id`. The description adds no extra meaning for the parameters themselves, mentioning only the returned fields rather than the input `id` or `merchant_id`. With full schema coverage, the baseline of 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?

The description uses a specific verb and resource — 'Reads one catalogue directory in full' — and enumerates exactly what is returned: settings, `content_md`, sub-directories, and the sessions matched by the tag filter. This clearly differentiates it from the sibling `list_catalogue_directories` because it targets a single directory and from `update_catalogue_directory` because it is a read operation.

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?

The description explicitly states when to use this tool: 'Read a directory before updating it' and explains why — the fields are 'replaced wholesale' by updates. It also gives the verification use case of checking whether a session's tags place it in a directory. However, it does not name the alternative tool to use when a list is needed or specify when not to use this tool.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools target distinct resources and actions, with clear category prefixes like [Interviews], [Results], and [Admin]. A few pairs could be confused—create_interview vs. create_interview_from_questions and update_interview vs. set_interview_state—but the descriptions do enough to separate them.

Naming Consistency4/5

The overwhelming majority follow a consistent verb_noun pattern: create_*, get_*, list_*, update_*, generate_*. The main deviation is jobmojito_configuration, which is a noun phrase rather than an action verb, and a few longer names like request_another_interview_attempt break the clean pattern slightly.

Tool Count2/5

With 29 tools, this server is above the 25+ threshold and places a significant navigation burden on an agent. The tools are organized into coherent domains, but several admin/merchant and results tools could likely be consolidated.

Completeness3/5

The core interview lifecycle is well covered: create, read, update, list, state changes, result retrieval, and report generation. However, there are notable gaps such as no delete operations for interviews or catalogue directories, no candidate management beyond listing/registration, and no explicit result-decision tool.

Get coaching catalogue directory

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources