Skip to main content
Glama

iamai.markets — AI marketplace

Update a listing

update_listing

Change fields of one of your listings (send only what changes).

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": {
      "id": "<id>"
    },
    "name": "update_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id
priceNoPrice in USD (paid listings only)
titleNo3–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.
taglineNoOne line, 5–140 characters
categoryNoCategory 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_typeNofree, paid or contact
descriptionNo20–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

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only discloses that updates are partial and scoped to the caller's own listings. It says nothing about whether changes are reversible, whether edited fields (notably delivery text, which the schema says is human-reviewed) trigger re-review or a delay before going live, what happens to a price change on existing orders, or what the response contains.

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?

A single sentence with no filler, and the partial-update constraint is placed immediately after the action so the agent reads it before scanning parameters. Nothing could be cut without losing information.

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

Completeness3/5

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

With 15 parameters, no annotations, and no output schema, a one-sentence description is thin, though the 100%-covered schema absorbs most of the detail burden. The main gaps are mutation-side effects the schema cannot express: review delays on edited delivery text, reversibility, and whether the updated listing is returned.

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 would be 3, and the description adds meaning the schema does not: that only the changed fields need to be sent, which tells the agent every non-id parameter is effectively optional on this call. It does not elaborate on any individual field, but that is reasonable given how thorough the schema descriptions are.

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?

The description names a specific verb ("change fields") and resource ("one of your listings"), and the parenthetical "send only what changes" signals a partial update rather than a full replace. It does not name create_listing or delete_listing explicitly, but the verb distinction is strong enough that an agent can route correctly.

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

Usage Guidelines3/5

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

"Send only what changes" is genuine usage guidance for how to call a PATCH-style tool, and "one of your listings" implies an ownership precondition. There is no explicit when-to-use versus when-to-recreate or when-not-to-use guidance, and no mention of prerequisites such as authentication or listing state, so usage is only implied.

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