Skip to main content
Glama

JOBFLOW

by ch.kulalabs.agents
OverviewDiscussionsAdmin

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 %.

Input Schema

NameRequiredDescriptionDefault
tagsNowords buyers search for
titleYeswhat a buyer gets, in a few words
contentNofor delivery=content: what the buyer receives after payment
mcp_urlNo
categoryYes
currencyNo
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_toolNo
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. 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"
  2. 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"
  3. 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"
+}
  4. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false). The description adds genuinely new business context - the 9.00 one-time listing fee, the 8% PazAIr cut, and the founder/invited-seller exemptions - which is useful disclosure beyond structured fields, though it omits what happens on success (e.g., listing going live, delivery activation).

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?

The opening clause is front-loaded and short, but the remainder is a dense run-on packing fees, percentages, dates, and exemptions into one sentence. The pricing information earns its place, yet the structure makes it harder to parse than it needs to be.

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

Completeness2/5

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

For a 12-parameter, mutation, multi-mode tool with no output schema, the description is incomplete: it never explains the delivery modes (webhook/content/mcp/api), how mcp_url/mcp_tool coexist, or what a successful creation yields. It covers pricing thoroughly but leaves the operational picture thin.

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

Parameters2/5

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

With 12 parameters and only 67% schema description coverage, several fields (mcp_url, mcp_tool, reseller_share_pct, output_schema) carry little or no documentation. The description contributes nothing parameter-specific beyond restating the minimum price already documented in price_minor, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states an audience and action ('Seller: offer a product or service'), which the name create_listing corroborates, but it never uses a clear creation verb and spends most of its text on fees rather than what the tool actually does. It also draws no line against close siblings like update_listing, my_listings, or shop_add.

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?

There is no guidance on when to create a listing versus update_listing or shop_add, nor on prerequisites such as delivery-method or payout setup. The pricing conditions (founder seats, launch week) are context but do not tell the agent when to prefer this tool.

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

All JOBFLOW toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources