Skip to main content
Glama

Publish a listing

publish_listing
Idempotent

Publishes the listing prepared by prepare_listing, after the user said yes to its summary question for THIS card: pass the dealId, the publishToken and confirm true. Never call it without that yes. The result says whether the listing is confirmed live (with its link) or submitted and not confirmed yet; say exactly that. A retry returns the same listing. If the result has alerts, show them to the user before anything else.

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": {
      "dealId": "<dealId>",
      "publishToken": "<publishToken>",
      "confirm": "<confirm>"
    },
    "name": "publish_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealIdYesThe dealId from prepare_listing.
confirmYesTrue once the user said yes to this listing; never set it before that.
publishTokenYesThe publishToken from prepare_listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true; the description reinforces idempotency ('a retry returns the same listing') and adds genuinely new behavioral context about the two possible outcomes (confirmed live with a link vs. submitted-but-not-confirmed) and the alerts-surfaced-first rule. It does not cover failure modes or authorization requirements, which keeps it short of 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-loads the action and the consent gate, then covers result handling and alert ordering in a compact sequence with no filler. The presentation instructions ('say exactly that', 'show them to the user before anything else') are purposeful given there is no output schema, though the sentences are somewhat dense.

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?

With no output schema, the description correctly takes on the burden of describing return states and the alerts-first display requirement, and the consent precondition is fully specified. What remains unaddressed—error behavior and permission requirements—is modest for a tool whose annotations already declare openness and non-destructiveness.

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 coverage is 100% and each parameter already documents its origin ('the dealId from prepare_listing', 'the publishToken from prepare_listing', the confirm gate). The description mainly restates the same values, adding only the 'for THIS card' scoping nuance, so the schema does the heavy lifting and the baseline applies.

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 ('publishes the listing') and ties it directly to the sibling that produces its inputs ('prepared by prepare_listing'). An agent can distinguish this from prepare_listing, listing_checkup, and my_listings without opening any schema.

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?

Gives an explicit precondition and an explicit prohibition: only call after the user said yes to the summary question for THIS card, and 'Never call it without that yes.' The upstream dependency on prepare_listing is named, so the ordering of calls is unambiguous.

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