Joomil — Swiss Classifieds MCP

get_categories

Read-only

List active categories of the Joomil.ch marketplace. Returns a flat list with parent_id for hierarchy reconstruction. Omit parent_id for all categories, use parent_id=0 for root categories only, or pass a specific ID to get direct children of that category.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`parent_id`	No	Filter to direct children of this category ID. Omit for all categories. Use 0 for root categories only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`categories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "categories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "ad_count": {
+            "type": "number"
+          },
+          "allow_ads": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "parent_id": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "url",
+          "parent_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "categories",
+    "total"
+  ],
+  "type": "object"
+}

First observedApr 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Since annotations already declare readOnlyHint=true and destructiveHint=false, the description adds extra value by revealing the 'active' filter, the flat list structure, and how parent_id supports hierarchy reconstruction. This gives the agent a clear mental model of the response shape and filtering semantics, going beyond the annotated safety profile.

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?

Two sentences, no redundancy. The first states the core purpose; the second delivers all necessary parameter guidance in a compact, scannable format. Every word earns its place.

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 simple read-only list tool with one optional parameter, an output schema, and clear annotations, the description covers all essential aspects: what is returned (flat list with parent_id), how to filter, and the 'active' constraint. No critical information 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?

The input schema already describes parent_id with 100% coverage, including the exact semantics for omission, 0, and specific IDs. The description repeats this information nearly verbatim and adds no new parameter-level insight, so it does not elevate above the schema baseline.

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 opens with a specific verb ('List') and resource ('active categories of the Joomil.ch marketplace'), clearly distinguishing this from sibling tools like get_cantons or search_classifieds. It also immediately signals the return type (flat list) and key attribute (parent_id), leaving zero ambiguity about the tool's function.

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 provides explicit guidance on when to use different parameter values (omit, 0, specific ID), covering the main usage scenarios. It doesn't explicitly mention when not to use this tool or alternatives, but the domain is distinct enough that a knowledgeable agent would infer the correct choice. The parameter guidance is a strong substitute for direct alternatives.

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

All Joomil — Swiss Classifieds MCP 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.