Skip to main content
Glama

Joomil — Swiss Classifieds MCP

get_classified

Read-only

Get full details of a single classified ad on Joomil.ch by its numeric ID. Returns complete description, all images URLs, category breadcrumb (full_path), vendor info (name, certified status, pro company), expiry date and boost level. Use search_classifieds first to find relevant listing IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric listing ID — visible in the URL and in search_classifieds results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlYes
boostYes
priceYes
titleYes
imagesYes
sellerYes
categoryYes
locationYes
created_atYes
expires_atYes
descriptionYes
has_pictureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "boost": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "category": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "id": {
      +              "type": "number"
      +            },
      +            "name": {
      +              "type": "string"
      +            },
      +            "path": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "name",
      +            "url",
      +            "path"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "created_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "description": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "expires_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "has_picture": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "number"
      +    },
      +    "images": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "location": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "canton": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "city": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "postal_code": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "city",
      +        "postal_code",
      +        "canton",
      +        "country"
      +      ],
      +      "type": "object"
      +    },
      +    "price": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "amount": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "currency": {
      +          "const": "CHF",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "amount",
      +        "currency"
      +      ],
      +      "type": "object"
      +    },
      +    "seller": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "certified": {
      +          "type": "boolean"
      +        },
      +        "company": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "name": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "type": {
      +          "enum": [
      +            "pro",
      +            "private"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "certified",
      +        "type",
      +        "company"
      +      ],
      +      "type": "object"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "title",
      +    "description",
      +    "price",
      +    "location",
      +    "category",
      +    "url",
      +    "created_at",
      +    "has_picture",
      +    "seller",
      +    "images",
      +    "expires_at",
      +    "boost"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by detailing the returned data (full description, images, category path, vendor info), which goes beyond the annotations and helps set expectations for the response.

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 with no redundancy: first states the operation and inputs, second lists key return fields and a usage tip. The description is front-loaded and every sentence contributes value.

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 an output schema present and only one simple parameter, the description fully covers the necessary context. It explains what is returned, ties to the search workflow, and matches the read-only nature of the tool. No gaps are apparent.

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 coverage is 100% with the 'id' parameter already well described in the schema (numeric, found in URL and search results). The description does not need to add parameter details, and the baseline of 3 applies because the schema carries the full burden.

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 clearly specifies a single classified ad retrieval by numeric ID, listing the exact fields returned (description, images, breadcrumb, vendor info, expiry, boost level). It distinguishes itself from search_classifieds by focusing on a single listing, making the purpose unmistakable.

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?

Explicitly instructs to use search_classifieds first to find listing IDs, providing a clear prerequisite and workflow. While it doesn't exhaustively list when-not-to-use, this guidance is sufficient for the tool's simple read-only role.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.