Skip to main content
Glama

submit_listing

Older name for buy_listing, kept so existing agents keep working. Starts a
Hokai listing and returns a payment link (checkout_url, also given as
payment_url). Nothing is charged by this call. Refunds are not automatic:
ask damien@hokai.io.

Args:
    tool_url: the product's own website, e.g. https://example.com
    email: a work email for the vendor
    company: company name (optional)
    note: anything the editors should know (optional)

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": {
      "tool_url": "<tool_url>",
      "email": "<email>"
    },
    "name": "submit_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
emailYes
companyNo
tool_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 that a listing is started, that a payment link is returned under two field names, that 'Nothing is charged by this call', and that refunds are not automatic with a contact address. It omits auth requirements and idempotency/retry behavior, which keeps it from 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.

Conciseness4/5

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

Front-loaded with the alias relationship, followed by behavior and then a compact Args list; nearly every sentence earns its place. The parenthetical about checkout_url/payment_url is slightly redundant but resolves a real ambiguity for the caller.

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 4-parameter mutation tool with no annotations and no output schema, the description covers the side effect, the return value, cost, and refund policy, which is enough to call it correctly. Auth/prerequisite information is the main remaining gap.

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 description coverage is 0%, so the Args block is doing real work: all four parameters are explained, the two required ones are implied by their lack of an '(optional)' marker, and tool_url gets a concrete format example. The explanations are terse (what constitutes a valid 'work email' or acceptable URL is unstated), so not a 5.

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?

States a specific verb and resource ('Starts a Hokai listing') and immediately identifies itself as the older name for the sibling buy_listing, so an agent can tell exactly what it does and how it relates to the other tool.

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?

The opening line 'kept so existing agents keep working' frames the intended audience and indirectly points new work at buy_listing, which is clear context. It stops short of an explicit instruction such as 'prefer buy_listing for new integrations', so it is strong but not a full when/when-not statement.

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