Skip to main content
Glama

DACIX — The Store for AI Agents

by store.dacix
OverviewDiscussionsAdmin

post_classified_ad

Publish a real classified ad on micapublicitate.online (Romanian classifieds, 30-day listing, free listings only). Returns the public URL. 20 credits, charged only when the ad is accepted. Requires a funded account (signup credits do not cover ads), an advertiser name and a reachable contact: telefon or contact_email. Each DACIX customer posts under their own classifieds account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orasNoCity (optional)
judetNoCounty (optional)
titleYesAd title (10-255 chars)
api_keyYesYour DACIX API key (dacix_sk_...). Get one with store_register.
telefonNoPhone shown on the ad, e.g. +40721234567
websiteNoLink shown on the ad (optional, no placeholder domains)
tip_ofertaNovanzare
category_idYesFrom classified_categories
descriptionYesAd text, plain or simple HTML (min 30 chars)
nume_contactYesAdvertiser name shown on the ad
contact_emailNoContact email

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / contact_email / description
      Previous value: -"Contact email (optional)"New value: +"Contact email"
    • addedInput schema / properties / nume_contact
      Added value: +{
+  "description": "Advertiser name shown on the ad",
+  "type": "string"
+}
    • removedInput schema / properties / price
      Removed value: -{
-  "description": "Price in RON (optional)",
-  "type": "number"
-}
    • addedInput schema / properties / telefon
      Added value: +{
+  "description": "Phone shown on the ad, e.g. +40721234567",
+  "type": "string"
+}
    • changedInput schema / properties / website / description
      Previous value: -"Link shown on the ad (optional)"New value: +"Link shown on the ad (optional, no placeholder domains)"
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "title",
-  "description",
-  "category_id"
-]New value: +[
+  "api_key",
+  "title",
+  "description",
+  "category_id",
+  "nume_contact"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and discloses substantial behavioral detail: 30-day listing lifetime, free listings only, 20 credits charged only upon acceptance, funded-account requirement, and per-customer classifieds account isolation. It also states the return value (public URL), which goes well beyond a generic 'post an ad' statement.

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?

Five short sentences, each carrying a distinct fact: what the tool does, what it returns, cost and charge timing, prerequisites, and account ownership. There is no filler, repetition, or unnecessary restating of schema fields.

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 an 11-parameter tool with no output schema and no annotations, the description covers all essential non-schema behavior: return URL, pricing, conditional charging, funding precondition, and account scoping. Combined with the high-coverage schema, an agent has enough information to invoke the tool correctly.

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

Parameters4/5

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

Schema description coverage is 91%, so most parameters are already documented in the schema. The description adds a valuable constraint not visible in the schema: although telefon and contact_email are structurally optional, at least one reachable contact is required, and it maps 'advertiser name' to nume_contact.

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 and resource: 'Publish a real classified ad on micapublicitate.online', and adds concrete scope (Romanian classifieds, 30-day listing, free listings only). This clearly distinguishes the tool from sibling store, account, and SEO tools.

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 gives clear prerequisites for use: a funded account, an advertiser name, and a reachable contact (telefon or contact_email), while noting that signup credits are insufficient. It does not explicitly name alternatives or state when not to use this tool, so exclusion guidance is missing.

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

All DACIX — The Store for AI Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources