Skip to main content
Glama

create_draft

Creates the publish draft (it fails if one already exists: carry on with update_draft or delete it with delete_draft). The fields are those of the /vender assistant, IMAGES INCLUDED (gallery and bannerUrl with the paths from image_upload_link), and the INPUT SCHEMA already carries the allowed values and the limits of each one: category and platforms are closed lowercase lists, the price is a number and the licence is standard or exclusive. There is no article to read first: whatever is not in the schema is not required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPublic name of the template, 1 to 80 characters.
tagsNoSearch tags, 1 to 5, of up to 28 characters (free text).
priceNoRegular price in USDC, a NUMBER (49, 49.5), from 1 to 100000. The same number as text ("49") is also accepted and normalized.
stackNoTechnologies of the product (free text, 1 to 5 items of up to 30 characters): "Next.js", "PostgreSQL"…
demoUrlNoLive demo: full http(s) URL.
galleryNoImages of the product: 3 to 20 PATHS returned by image_upload_link (/api/media/template-media/…/x.webp). Aspect ratio 4:3 (tolerance ±4 %), recommended 1600x1200 px: the same one the /vender wizard crops the web images to. Anything that does not fit is REJECTED on submit ([IMAGEN_PROPORCION], with the size it had); it is not cropped for you, the framing is yours. image_upload_link repeats it in its answer with the live measurements and check_before_submit checks it before spending the submission. External URLs and other formats are not valid (old templates keep URLs from the former public Vercel Blob host: they are still accepted, but they no longer serve any image).
supportNoSupport contact, ONE single value: the email if supportKind is "email", the http(s) URL if it is "url". When it is submitted for review it travels split into supportEmail or supportUrl.
taglineNoSHORT description (the one shown on the catalog card), 1 to 200 characters.
categoryNoCatalog category. Closed list, lowercase and without accents: only one of these values.
includesNo"What's included": 1 to 4 bullet points of up to 120 characters each.
bannerUrlNoCover image: a PATH from image_upload_link, just like the gallery ones and with the SAME aspect ratio. Aspect ratio 4:3 (tolerance ±4 %), recommended 1600x1200 px: the same one the /vender wizard crops the web images to. Anything that does not fit is REJECTED on submit ([IMAGEN_PROPORCION], with the size it had); it is not cropped for you, the framing is yours. image_upload_link repeats it in its answer with the live measurements and check_before_submit checks it before spending the submission.
platformsNoTarget platforms, 1 to 7. Closed list, lowercase: only these values.
descriptionNoLONG description of the listing. Simple HTML is allowed (the server sanitizes it) with your own images as <img src="/api/media/…">, 1 to 100000 characters. AGENT ACCOUNTS also have two caps of their own from the pre-filter: 8000 plain text characters and 50 links.
licenseTypeNoSale licence. `standard` (the site calls it "Standard"): sold as many times as you want. `exclusive` ("Exclusive"): sale exclusivity, sold ONCE, it leaves the catalog and is never resold on any platform. IT CANNOT BE CHANGED AFTER PUBLISHING. Without this field it is published as `standard`. The old names `recurrente` and `unica` are still accepted.
nativeLangsNoNATIVE languages of the application being sold (not the language of the listing), 1 to 8. Two letter ISO codes, closed list: es, en, fr, de, it, nl, pt, id.
supportKindNoWhat `support` is: "email" (an email address) or "url" (a link). Only these two values.
youtubeLinksNoVideos: up to 3 YouTube links (the server extracts the id). Videos are NOT uploaded.
discountPriceNoDiscounted price, same format and same range as price, and STRICTLY LOWER than it. It is the effective sale price.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: the draft has been created.
draftYesThe saved draft, read in the MCP vocabulary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • changedInput schema / description
      Previous value: -"Campos del borrador (hay UNO por cuenta y lo comparte con el asistente /vender). Todos son opcionales: el borrador se va rellenando a trozos y my_draft dice qué falta para poder enviarlo. Límites y obligatorios VIGENTES en la plataforma: se leen al responder tools/list y el admin puede cambiarlos (vuelve a pedir tools/list; el error de la validación trae siempre la cifra viva). / Draft fields; all optional, my_draft lists what is still missing. Limits and required fields are the platform's current ones, read when tools/list is answered."New value: +"Draft fields (there is ONE per account and it is shared with the /vender wizard). They are all optional: the draft is filled in piece by piece and my_draft says what is missing before it can be submitted. Limits and required fields are the CURRENT ones on the platform: they are read when tools/list is answered and the admin can change them (ask for tools/list again; the validation error always carries the live figure)."
    • changedInput schema / properties / bannerUrl / description
      Previous value: -"Imagen de portada: una RUTA de image_upload_link, igual que las de gallery y con la MISMA proporción. Proporción 4:3 (tolerancia ±4 %), recomendado 1600x1200 px: es la misma a la que el asistente /vender recorta las imágenes de la web. Lo que no encaje se RECHAZA al enviar ([IMAGEN_PROPORCION], con las medidas que tenía); no se recorta por ti, el encuadre es tuyo. image_upload_link lo repite en su respuesta con las medidas vivas y check_before_submit lo comprueba antes de gastar el envío. / Cover image path from image_upload_link, same 4:3 aspect ratio."New value: +"Cover image: a PATH from image_upload_link, just like the gallery ones and with the SAME aspect ratio. Aspect ratio 4:3 (tolerance ±4 %), recommended 1600x1200 px: the same one the /vender wizard crops the web images to. Anything that does not fit is REJECTED on submit ([IMAGEN_PROPORCION], with the size it had); it is not cropped for you, the framing is yours. image_upload_link repeats it in its answer with the live measurements and check_before_submit checks it before spending the submission."
    • changedInput schema / properties / category / description
      Previous value: -"Categoría del catálogo. Lista cerrada, en minúsculas y sin acentos: solo uno de estos valores. / Catalog category; closed list, lowercase, exactly one of these values."New value: +"Catalog category. Closed list, lowercase and without accents: only one of these values."
    • changedInput schema / properties / demoUrl / description
      Previous value: -"Demo en vivo: URL http(s) completa. / Live demo; full http(s) URL."New value: +"Live demo: full http(s) URL."
    • changedInput schema / properties / description / description
      Previous value: -"Descripción LARGA de la ficha. Admite HTML sencillo (el servidor lo sanea) con imágenes propias como <img src=\"/api/media/…\">, 1 a 100000 caracteres. Las CUENTAS-AGENTE tienen además dos topes propios del prefiltro: 8000 caracteres de texto plano y 50 enlaces. / Long description, 1 to 100000 characters; simple HTML allowed and sanitized server side. Agent accounts also have their own pre-filter caps: 8000 plain text characters and 50 links."New value: +"LONG description of the listing. Simple HTML is allowed (the server sanitizes it) with your own images as <img src=\"/api/media/…\">, 1 to 100000 characters. AGENT ACCOUNTS also have two caps of their own from the pre-filter: 8000 plain text characters and 50 links."
    • changedInput schema / properties / discountPrice / description
      Previous value: -"Precio con descuento, mismo formato y mismo rango que price, y ESTRICTAMENTE MENOR que él. Es el precio efectivo de venta. / Discounted price; same range as price and strictly lower than it."New value: +"Discounted price, same format and same range as price, and STRICTLY LOWER than it. It is the effective sale price."
    • changedInput schema / properties / gallery / description
      Previous value: -"Imágenes del producto: 3 a 20 RUTAS devueltas por image_upload_link (/api/media/template-media/…/x.webp). Proporción 4:3 (tolerancia ±4 %), recomendado 1600x1200 px: es la misma a la que el asistente /vender recorta las imágenes de la web. Lo que no encaje se RECHAZA al enviar ([IMAGEN_PROPORCION], con las medidas que tenía); no se recorta por ti, el encuadre es tuyo. image_upload_link lo repite en su respuesta con las medidas vivas y check_before_submit lo comprueba antes de gastar el envío. No valen URLs externas ni otros formatos (las plantillas viejas conservan URLs del antiguo host público de Vercel Blob: se siguen aceptando, pero ya no sirven imágenes). / Product images: 3 to 20 paths returned by image_upload_link, WebP only, 4:3 aspect ratio (±4 %); anything else is rejected on submit."New value: +"Images of the product: 3 to 20 PATHS returned by image_upload_link (/api/media/template-media/…/x.webp). Aspect ratio 4:3 (tolerance ±4 %), recommended 1600x1200 px: the same one the /vender wizard crops the web images to. Anything that does not fit is REJECTED on submit ([IMAGEN_PROPORCION], with the size it had); it is not cropped for you, the framing is yours. image_upload_link repeats it in its answer with the live measurements and check_before_submit checks it before spending the submission. External URLs and other formats are not valid (old templates keep URLs from the former public Vercel Blob host: they are still accepted, but they no longer serve any image)."
    • changedInput schema / properties / includes / description
      Previous value: -"«Qué incluye»: 1 a 4 puntos de hasta 120 caracteres cada uno. / What's included: 1 to 4 short bullet points."New value: +"\"What's included\": 1 to 4 bullet points of up to 120 characters each."
    • changedInput schema / properties / licenseType / description
      Previous value: -"Licencia de venta. `standard` (la web la llama «Estándar»): se vende tantas veces como quieras. `exclusive` («Exclusiva»): exclusividad de venta, se vende UNA vez, sale del catálogo y no se revende en ninguna plataforma. NO SE PUEDE CAMBIAR DESPUÉS DE PUBLICAR. Sin este campo se publica como `standard`. Se siguen aceptando los nombres antiguos `recurrente` y `unica`. / Sale licence: `standard` sells many times; `exclusive` sells once and may never be resold anywhere. Cannot be changed after publishing; defaults to `standard`. Legacy values `recurrente` and `unica` are still accepted."New value: +"Sale licence. `standard` (the site calls it \"Standard\"): sold as many times as you want. `exclusive` (\"Exclusive\"): sale exclusivity, sold ONCE, it leaves the catalog and is never resold on any platform. IT CANNOT BE CHANGED AFTER PUBLISHING. Without this field it is published as `standard`. The old names `recurrente` and `unica` are still accepted."
    • changedInput schema / properties / name / description
      Previous value: -"Nombre público de la plantilla, 1 a 80 caracteres. / Public template name, 1 to 80 characters."New value: +"Public name of the template, 1 to 80 characters."
    • changedInput schema / properties / nativeLangs / description
      Previous value: -"Idiomas NATIVOS de la aplicación que se vende (no el idioma de la ficha), 1 a 8. Códigos ISO de dos letras, lista cerrada: es, en, fr, de, it, nl, pt, id. / Languages the delivered app itself ships with, 1 to 8; two letter codes, closed list."New value: +"NATIVE languages of the application being sold (not the language of the listing), 1 to 8. Two letter ISO codes, closed list: es, en, fr, de, it, nl, pt, id."
    • changedInput schema / properties / platforms / description
      Previous value: -"Plataformas objetivo, 1 a 7. Lista cerrada, en minúsculas: solo estos valores. / Target platforms, 1 to 7; closed list, lowercase."New value: +"Target platforms, 1 to 7. Closed list, lowercase: only these values."
    • changedInput schema / properties / price / description
      Previous value: -"Precio regular en USDC, NÚMERO (49, 49.5), de 1 a 100000. También se acepta el mismo número como texto (\"49\") y se normaliza. / Regular price in USDC as a number, 1 to 100000; a numeric string is accepted and normalized."New value: +"Regular price in USDC, a NUMBER (49, 49.5), from 1 to 100000. The same number as text (\"49\") is also accepted and normalized."
    • changedInput schema / properties / stack / description
      Previous value: -"Tecnologías del producto (texto libre, 1 a 5 elementos de hasta 30 caracteres): \"Next.js\", \"PostgreSQL\"… / Tech stack, 1 to 5 free text items."New value: +"Technologies of the product (free text, 1 to 5 items of up to 30 characters): \"Next.js\", \"PostgreSQL\"…"
    • changedInput schema / properties / support / description
      Previous value: -"Contacto de soporte, UN solo valor: el correo si supportKind es \"email\", la URL http(s) si es \"url\". Al enviar a revisión viaja separado en supportEmail o supportUrl. / Support contact value; its kind is supportKind."New value: +"Support contact, ONE single value: the email if supportKind is \"email\", the http(s) URL if it is \"url\". When it is submitted for review it travels split into supportEmail or supportUrl."
    • changedInput schema / properties / supportKind / description
      Previous value: -"Qué es `support`: \"email\" (correo) o \"url\" (enlace). Solo estos dos valores. / What `support` holds: email address or link."New value: +"What `support` is: \"email\" (an email address) or \"url\" (a link). Only these two values."
    • changedInput schema / properties / tagline / description
      Previous value: -"Descripción CORTA (la que se ve en la tarjeta del catálogo), 1 a 200 caracteres. / Short one line description shown on the catalog card, 1 to 200 characters."New value: +"SHORT description (the one shown on the catalog card), 1 to 200 characters."
    • changedInput schema / properties / tags / description
      Previous value: -"Etiquetas de búsqueda, 1 a 5, de hasta 28 caracteres (texto libre). / Search tags, 1 to 5; free text."New value: +"Search tags, 1 to 5, of up to 28 characters (free text)."
    • changedInput schema / properties / youtubeLinks / description
      Previous value: -"Vídeos: hasta 3 enlaces de YouTube (el servidor extrae el id). Los vídeos NO se suben. / YouTube links, up to 3; videos are never uploaded."New value: +"Videos: up to 3 YouTube links (the server extracts the id). Videos are NOT uploaded."
    • changedOutput schema / properties / draft / description
      Previous value: -"El borrador guardado, leído en el vocabulario del MCP."New value: +"The saved draft, read in the MCP vocabulary."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: el borrador se ha creado."New value: +"Always true: the draft has been created."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

There are no annotations, so the description carries the behavioral burden. It discloses the key non-obvious behavior: the call fails if a draft already exists, implying it never overwrites. It does not mention broader lifecycle details such as auth or where the draft appears afterward, but the critical failure mode is covered.

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?

The description is three tight sentences. The failure condition is front-loaded, then the schema pointer, then a clear statement that nothing else is required. Every sentence earns its place and there is no filler.

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?

Despite having 18 parameters, the input schema is extremely detailed and the tool has an output schema, so the description does not need to re-explain fields or return values. It supplies what the schema cannot: the failure-if-exists behavior, sibling routing, and the reassurance that anything not in the schema is not required. This is complete for the agent to call it 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 coverage is 100%, so a baseline of 3 applies. The description adds useful cross-parameter context above that baseline: gallery and bannerUrl must use paths from image_upload_link, category and platforms are closed lowercase lists, price must be a number, and licenseType is standard or exclusive. This helps the agent understand recurring constraints without duplicating the schema.

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 uses a specific verb and resource: 'Creates the publish draft'. It also distinguishes itself from siblings by stating that it fails if a draft already exists, and names update_draft and delete_draft as the alternatives. This makes the tool's purpose and scope unambiguous.

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

Usage Guidelines5/5

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

It explicitly tells the agent what to do when a draft already exists: 'carry on with update_draft or delete it with delete_draft'. It also directs the agent to rely on the input schema for values and limits, and clarifies that no external article or prerequisite is needed.

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