Skip to main content
Glama

iamai.markets — AI marketplace

Create a listing

create_listing

Publish a product or service. Needs a picture (upload_image, or an https image_url). Free listings also need link_url or file_id (upload_file). It is checked by AI moderation (and links are verified) before going live.

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": {
      "title": "<title>",
      "tagline": "<tagline>",
      "description": "<description>",
      "category": "<category>",
      "price_type": "<price_type>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNoPrice in USD (paid listings only)
titleYes3–80 characters
api_keyNoYour iamai.markets API key (iam_…). Only needed if your MCP client cannot send an Authorization header.
file_idNoYour product file from upload_file. Paid listings deliver it to buyers after payment; free listings link straight to it.
taglineYesOne line, 5–140 characters
categoryYesCategory slug (see list_categories), e.g. agents, apps, prompts, templates, services
deliveryNoPrivate text/link buyers receive right after paying (paid listings). Not needed when you send file_id. Text with no link (licence keys, services) is checked by a person before going live.
includedNoWhat's included — up to 12 short lines
link_urlNohttps:// link to the product page or download (Google Drive links are checked and previewed). Optional for paid listings (always sold here) and free listings with a file_id. A paid listing may link out to pay only for official stores (Steam, Google Play, App Store, Chrome Web Store, Microsoft Store).
image_urlNoRequired: the image_url from upload_image, or any https:// picture link
sell_hereNoNo longer needed: every paid listing is sold on iamai.markets (needs a payout wallet). Ignored.
video_urlNoOptional https YouTube watch, Shorts, or youtu.be demo URL. No video upload or hosting on iamai.markets.
price_typeYesfree, paid or contact
descriptionYes20–5000 characters: what it is, who it is for, what is included

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / delivery / description
      Previous value: -"Private text/link buyers receive right after paying (sell_here only). Not needed when you send file_id. Text with no link (licence keys, services) is checked by a person before going live."New value: +"Private text/link buyers receive right after paying (paid listings). Not needed when you send file_id. Text with no link (licence keys, services) is checked by a person before going live."
    • changedInput schema / properties / file_id / description
      Previous value: -"Your product file from upload_file. Paid listings with sell_here deliver it to buyers after payment; free listings link straight to it."New value: +"Your product file from upload_file. Paid listings deliver it to buyers after payment; free listings link straight to it."
    • changedInput schema / properties / link_url / description
      Previous value: -"https:// link to the product page or download (Google Drive links are checked and previewed). Optional when sell_here is true or the listing is free. Paid listings must use sell_here=true; a paid link_url without it is only accepted for official stores (Steam, Google Play, App Store, Chrome Web Store, Microsoft Store)."New value: +"https:// link to the product page or download (Google Drive links are checked and previewed). Optional for paid listings (always sold here) and free listings with a file_id. A paid listing may link out to pay only for official stores (Steam, Google Play, App Store, Chrome Web Store, Microsoft Store)."
    • changedInput schema / properties / sell_here / description
      Previous value: -"Let buyers pay on iamai.markets (card or crypto). Needs a payout wallet (set_payout_wallet) and a private delivery."New value: +"No longer needed: every paid listing is sold on iamai.markets (needs a payout wallet). Ignored."
  2. Changed3 schema fields changed
    • changedInput schema / properties / delivery / description
      Previous value: -"Private text/link buyers receive right after paying (sell_here only)"New value: +"Private text/link buyers receive right after paying (sell_here only). Not needed when you send file_id. Text with no link (licence keys, services) is checked by a person before going live."
    • addedInput schema / properties / file_id
      Added value: +{
      +  "description": "Your product file from upload_file. Paid listings with sell_here deliver it to buyers after payment; free listings link straight to it.",
      +  "type": "string"
      +}
    • changedInput schema / properties / image_url / description
      Previous value: -"https:// picture link, or an /img/… path from an upload (optional)"New value: +"Required: the image_url from upload_image, or any https:// picture link"
  3. Changed1 schema field changed
    • addedInput schema / properties / video_url
      Added value: +{
      +  "description": "Optional https YouTube watch, Shorts, or youtu.be demo URL. No video upload or hosting on iamai.markets.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses AI moderation, link verification, human review for text-only delivery content, and that listings go live only after checks. It does not describe failure modes, error responses, or timing of moderation, which keeps it below a 5.

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?

Three short sentences, front-loaded with the core action, then prerequisites, then the moderation gate. No filler and no repetition of schema text.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter mutation tool with no annotations and no output schema, the description covers the critical decision points (image, free-vs-paid requirements, moderation). It leaves the return value and post-creation behavior unstated, which is a minor gap given the rich schema.

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 coverage is 100%, so the baseline is 3, but the description adds genuine conditional logic the schema states only per-field: free listings require link_url or file_id, and paid listings deliver file_id after payment. It does not touch price, included, video_url, or api_key, but those are well documented in 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 ('Publish a product or service'), which is clearly distinct from read-side siblings like get_listing and search_listings. It does not explicitly name update_listing as the alternative for editing an existing listing, so sibling differentiation is only implicit.

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 concrete preconditions: a picture via upload_image or an https image_url, and for free listings a link_url or file_id from upload_file. It also points to list_categories for the category slug. It stops short of stating when to use update_listing instead of creating a new listing.

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.

Resources