eno.vn Partner API

create_listing

Create a listing. Image URLs may be public — they are re-hosted to first-party storage automatically.

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": {
      "categorySlug": "<categorySlug>",
      "title": "<title>"
    },
    "name": "create_listing"
  }
}

Input Schema

Name	Required	Description
`brand`	No
`model`	No
`price`	No	Price in VND — required, except for a job (category "jobs"), whose pay is `salaryM`. A job sent with only a price has it read as the monthly salary in VND.
`title`	Yes	Listing title (≥3 chars, no phone numbers)
`images`	No	Public image URLs — auto re-hosted to first-party storage
`salaryM`	No	A job (category "jobs"): the monthly salary in million VND; omit it when the pay is agreed with the candidate. A job's stored price is derived from it, and a job takes no offers.
`district`	No
`condition`	No	e.g. "new", "used"
`negotiable`	No
`description`	No
`listingType`	No
`categorySlug`	Yes	Category slug, e.g. "electronics"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one genuine side effect — public image URLs are re-hosted to first-party storage — but says nothing about write semantics, permissions/auth needs, failure modes, or the substantial category-specific behavior (jobs derive price from salaryM and take no offers).

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 short sentences, front-loaded with the core action, and the image-rehosting note placed immediately after. No filler or redundant restatement of the title.

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?

For a 12-parameter mutation tool with no annotations and no output schema, the description is far too thin. It omits the job/salaryM special case, required-field expectations, and half the parameters, leaving the agent to reconstruct behavior from the schema alone.

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 only 50%, so the description needs to compensate, and it does not. It only echoes the images parameter; brand, model, district, negotiable, description, and listingType remain undocumented in both places, and the price/salaryM interplay for jobs is left entirely to the schema.

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 and resource ("Create a listing") so the operation is unambiguous. However, it never distinguishes itself from close siblings like bulk_create_listings or update_listing, so the agent must infer the boundary from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to prefer bulk_create_listings for multiple items, and no prerequisites or preconditions (e.g. category must exist). The only guidance is an implicit note about image URLs, which is about input format rather than tool selection.

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

All eno.vn Partner API tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?