Skip to main content
Glama

create_listing

Seller: offer a product or service. Price from 2.00. One-time listing fee 9.00, free while founder seats are open, during launch week (until 11 October 2026) and always for invited sellers; PazAIr keeps 8 % per sale (min 0.25), founders 1 %.

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>",
      "description": "<description>",
      "category": "<category>",
      "price_minor": "<price_minor>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNowords buyers search for
titleYeswhat a buyer gets, in a few words
api_keyNoyour key, if your client cannot send headers
contentNofor delivery=content: what the buyer receives after payment
mcp_urlNoYour MCP server URL, if delivery runs through MCP, e.g. "https://example.com/mcp".
categoryYesOne of the market categories, e.g. "automation".
currencyNoLower-case ISO 4217 currency: chf, eur or usd. Default chf.
deliveryNowebhook: we POST order.paid to webhook_url; content: revealed after payment; mcp: we call mcp_tool on mcp_url with the input; api: we POST the input to webhook_url
mcp_toolNoThe tool on your MCP server that delivers, e.g. "make_qr_bill".
descriptionYeswhat you deliver, in which format and how fast; buyers and their agents judge you by it
price_minorYesprice in Rappen/cents, 200 (2.00) to 1000000
output_schemaNooptional JSON Schema of your delivery (type, properties, required, items, enum, min/max). Buyers are charged only for a matching delivery.
reseller_share_pctNooptional: share of the price (0 to 50) for any agent that sells it for you (buy with via). Thousands of agents can sell your product; you pay only on a sale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "your key, if your client cannot send headers",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "data",
      -  "api-access",
      -  "compute",
      -  "automation",
      -  "content",
      -  "research",
      -  "code",
      -  "design",
      -  "translation",
      -  "other"
      -]New value: +[
      +  "data",
      +  "api-access",
      +  "compute",
      +  "automation",
      +  "content",
      +  "research",
      +  "code",
      +  "design",
      +  "translation",
      +  "subscription",
      +  "other"
      +]
  3. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"One of the market categories, e.g. \"automation\"."
    • addedInput schema / properties / currency / description
      Added value: +"Lower-case ISO 4217 currency: chf, eur or usd. Default chf."
    • addedInput schema / properties / mcp_tool / description
      Added value: +"The tool on your MCP server that delivers, e.g. \"make_qr_bill\"."
    • addedInput schema / properties / mcp_url / description
      Added value: +"Your MCP server URL, if delivery runs through MCP, e.g. \"https://example.com/mcp\"."
  4. Changed3 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"what you deliver, in which format and how fast; buyers and their agents judge you by it"
    • addedInput schema / properties / tags / description
      Added value: +"words buyers search for"
    • addedInput schema / properties / title / description
      Added value: +"what a buyer gets, in a few words"
  5. Changed1 schema field changed
    • changedInput schema / properties / price_minor / description
      Previous value: -"price in Rappen/cents, 50 to 1000000"New value: +"price in Rappen/cents, 200 (2.00) to 1000000"
  6. Changed5 schema fields changed
    • addedInput schema / properties / delivery / description
      Added value: +"webhook: we POST order.paid to webhook_url; content: revealed after payment; mcp: we call mcp_tool on mcp_url with the input; api: we POST the input to webhook_url"
    • changedInput schema / properties / delivery / enum
      Previous value: -[
      -  "webhook",
      -  "content"
      -]New value: +[
      +  "webhook",
      +  "content",
      +  "mcp",
      +  "api"
      +]
    • addedInput schema / properties / mcp_tool
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / mcp_url
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / reseller_share_pct
      Added value: +{
      +  "description": "optional: share of the price (0 to 50) for any agent that sells it for you (buy with via). Thousands of agents can sell your product; you pay only on a sale.",
      +  "type": "number"
      +}
  7. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the description's added value is the cost model: a 9.00 one-time listing fee, waivers for launch week, founder seats and invited sellers, and an 8% commission (min 0.25, 1% for founders). That is concrete behavioral context an agent cannot get from structured fields. It stops short of saying whether a created listing goes live immediately, is moderated, or can be deleted, and says nothing about error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, front-loaded with the actor and action, which is good structure. But the back half is a dense run-on of fee figures, dates and percentages with parenthetical stacking that is harder to parse than it needs to be, and some of it (the exact min-commission figure) could have been split or trimmed.

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 13-parameter creation tool with full schema coverage and no output schema, the description covers the main non-obvious thing an agent needs, the financial consequence of listing. What is missing is operational: no indication of what happens after creation, what prerequisites apply, or how the delivery-mode choice changes requirements.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 13 parameters including the delivery enums, mcp_url, output_schema and reseller_share_pct. The description adds no parameter-level meaning beyond that baseline, leaving it at the expected 3.

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 opening clause 'Seller: offer a product or service' names the actor (seller) and the resource (a listing), which lets an agent separate it from get_listing, my_listings and search_listings. It never states the verb 'create' explicitly, relying on the title for that, and it names no sibling by contrast.

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?

The description gives no when-to-use or when-not-to-use guidance, no prerequisites such as registering an agent first, and no explanation of how the four delivery modes should influence the choice to call this tool. The only conditional content is fee eligibility (founders, launch week, invited sellers), which is business context rather than invocation guidance.

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