Skip to main content
Glama

Pulltrader Seller Economics

by app.pulltrader

Compare trading-card seller proceeds across selling methods

compare_selling_costs

Compare estimated fees and the net amount a trading-card seller keeps when selling the SAME card across eBay (estimated), Pulltrader selling methods (marketplace, Fulfilled by Pulltrader, branded storefront, and in-person POS), and other marketplaces (TCGplayer, Mana Pool, Misprint, Fanatics Collect, Goldin — estimated fixed-price/Buy Now seller fees). Use this when a seller asks what they would keep/net/take-home on a sale, how fees compare between platforms, or which method leaves them with more money. Calculations are deterministic and use dated fee schedules. Competitor marketplaces are off by default; include them via the methods field. Only fixed-price seller fees are modeled — auction formats (hammer price, buyer's premium, negotiated consignment) are not. Do NOT use this to look up a card's market value or recent sales (this tool does not price cards), and do NOT use it for non-trading-card categories. Present competitor and eBay figures as estimates, never as guaranteed proceeds, and never claim one platform is universally cheapest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodsNoWhich selling methods to compare. Defaults to eBay, Pulltrader marketplace, and Pulltrader storefront. Other supported methods (off by default): pulltrader_fbp, pulltrader_pos, and estimated competitor marketplaces tcgplayer, manapool, misprint, fanatics_collect, goldin.
currencyNoISO currency code. Only USD is supported.USD
quantityNoNumber of identical items in one order. Per-order fixed fees are applied once.
sale_priceYesThe per-item sale price (the card's listed/sold price), in the given currency.
seller_planNoPulltrader seller plan. Determines the marketplace payout tier (free=91%, starter=93%, pro=94%, shop=95%).free
item_categoryNoItem category. Only trading_cards is supported.trading_cards
shipping_amountNoShipping amount charged to the buyer. Affects eBay's fee base. See assumptions for how each method treats shipping.
acquisition_costNoOptional. What the seller paid for the card; used to estimate net profit per method.
seller_covers_feesNoIf true, the seller absorbs the Pulltrader platform fee (3.25% + $0.40). If false (default), the buyer pays it at checkout. The platform fee is always charged on Pulltrader card sales regardless.
ebay_store_subscriptionNoIf true, estimate eBay fees using the eBay Store subscriber rate (12.35% up to $2,500/item) instead of the individual rate (13.25% up to $7,500/item).
ebay_fee_percent_overrideNoOptional. Override the estimated eBay final value fee percentage (e.g. for a seller with an eBay Store subscription).

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description covers behavioral traits: deterministic calculations using dated fee schedules, only fixed-price seller fees modeled, and eBay/competitor figures as estimates. Could add note about non-destructive nature but sufficient.

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?

Description is well-structured with front-loaded purpose, usage scenarios, and limitations. Slightly long but no fluff; every sentence adds value.

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?

Given 11 parameters and no output schema, description adequately explains tool scope, inputs, and limitations. Covers major usage scenarios and exceptions like auction formats not modeled.

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 100%, so baseline is 3. Description adds value by explaining default methods, that competitor methods are off by default, and how seller_plan affects payout tiers.

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?

The description clearly states the tool compares estimated fees and net proceeds across various trading-card selling methods. It distinguishes from siblings by focusing on selling method comparison, not pricing or identification.

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?

Explicitly specifies when to use (e.g., seller asks what they keep/net, how fees compare) and when not to use (not for market value, not for non-trading cards). Also clarifies that competitor methods are off by default.

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

All Pulltrader Seller Economics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct operation: calculating prices, comparing costs, explaining methods, identifying cards, searching sales, summarizing markets, and fetching price history. No functional overlap exists between any pair.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., calculate_required_sale_price, compare_selling_costs, explain_selling_method) with no mixed conventions or abbreviations.

Tool Count5/5

With 7 tools covering pricing, fee comparison, method explanations, card identification, sales search, market summary, and price history, the set is well-scoped for a seller economics domain—neither too sparse nor bloated.

Completeness5/5

The tool surface comprehensively covers the seller economics lifecycle: card identification, market data (recent sales, price history, summary), fee/cost comparison, target-pricing calculation, and method explanation. No obvious dead ends for the stated purpose.

Resources