Jiji MCP

jiji_prepare_advert

Prepares new or edited adverts for local owner review using Jiji’s current category form, without publishing listings, uploading photos, or selecting paid packages.

Instructions

Prepare a new or edited advert for local owner review using Jiji’s current category form. Upload photos directly on Jiji through the owner workflow first. Does not publish or upload files. Paid packages cannot be selected by this tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category_id": "<category_id>",
      "region_id": "<region_id>",
      "fields": "<fields>"
    },
    "name": "jiji_prepare_advert"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	Yes
`advert_id`	No
`region_id`	Yes
`category_id`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world behavior; the description adds meaningful context beyond them — output goes to owner review, files are not uploaded, and paid packages are blocked. It does not say whether repeated calls with the same advert_id overwrite or duplicate drafts, which matters given idempotentHint=false.

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

Conciseness4/5

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

Three short front-loaded sentences with no filler, the core action stated first. The photo-upload caveat precedes the negative constraints, which is a slightly less natural ordering but still tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 needn't be described, but with 0% schema coverage and an untyped nested 'fields' payload, the description leaves the agent unable to know how to populate the required parameters or what advert_id does. For a four-parameter write tool this is a substantial gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description supplies no parameter meaning at all. The free-form 'fields' object (additionalProperties with no shape) and the optional advert_id that presumably switches from create to edit are left entirely unexplained.

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 concrete verb+resource: preparing an advert for owner review, and clarifies it uses Jiji's current category form. It's distinguishable from siblings like jiji_prepare_action or jiji_open_workflow, though it doesn't explicitly name them.

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?

Gives clear prerequisites (upload photos through the owner workflow first) and exclusions (no publishing, no file upload, no paid packages). It stops short of naming which sibling tool to use when the agent does want to publish or apply a paid package.

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