Skip to main content
Glama
Sign In

freebox

by com.usefreebox
OverviewDiscussionsAdmin

Create an eBay arbitrage listing package

create_ebay_listing
Read-only

Takes a free find (by listing_id or title/resale value) and generates a complete, ready-to-sell eBay listing package including optimized SEO title, price recommendation, shipping viability, net profit breakdown, and pre-filled 1-click eBay sell URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_ebay_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoItem title (required if listing_id is omitted).
categoryNoItem category.
listing_idNoOptional listing id from find_free_stuff to convert.
est_resale_valueNoEstimated market price in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description's framing ('generates a package', 'pre-filled 1-click eBay sell URL') usefully clarifies that no live listing is published, resolving the tension with the 'create_' name. It stops short of stating the package is not persisted or how often it can be called.

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?

A single front-loaded sentence with the input forms first and the output payload second; every clause carries information. It is slightly dense as one run-on sentence but has no filler.

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 compensates well by enumerating the returned package (SEO title, price recommendation, shipping viability, net profit, sell URL). What is missing is what happens when no parameters are supplied at all (required count is zero), which an agent would need to know.

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%, so each parameter is already documented. The description's only addition is the conditional relationship between listing_id and title/resale value, which the schema hints at but does not express as a rule; category and est_resale_value semantics get no extra meaning.

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?

States a concrete verb and resource ('generates a complete, ready-to-sell eBay listing package') and enumerates what the package contains. It implicitly ties to find_free_stuff via 'takes a free find', but never names the sibling tool or the vault tools, so differentiation is left to inference.

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

Usage Guidelines3/5

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

The phrase 'takes a free find' plus 'by listing_id or title/resale value' implies the caller should first obtain a find, which is reasonable context. However, there is no explicit when-to-use/when-not guidance against siblings such as save_to_vault or my_vault, and the 'free find' wording is not connected to a named tool.

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

All freebox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources