Pulltrader Seller Economics
Server Details
Compare what a trading-card seller keeps across eBay, Pulltrader, and other card marketplaces.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.9/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools.
The single tool name follows a clear verb_noun pattern, which is consistent and informative.
The server is named 'Seller Economics' but only provides one tool, which is insufficient for the broad domain of seller economics.
The tool covers only fee comparison but lacks essential operations like listing management, order tracking, or account settings, leaving major gaps.
Available Tools
1 toolcompare_selling_costsCompare trading-card seller proceeds across selling methodsAInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| methods | No | Which 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. | |
| currency | No | ISO currency code. Only USD is supported. | USD |
| quantity | No | Number of identical items in one order. Per-order fixed fees are applied once. | |
| sale_price | Yes | The per-item sale price (the card's listed/sold price), in the given currency. | |
| seller_plan | No | Pulltrader seller plan. Determines the marketplace payout tier (free=91%, starter=93%, pro=94%, shop=95%). | free |
| item_category | No | Item category. Only trading_cards is supported. | trading_cards |
| shipping_amount | No | Shipping amount charged to the buyer. Affects eBay's fee base. See assumptions for how each method treats shipping. | |
| acquisition_cost | No | Optional. What the seller paid for the card; used to estimate net profit per method. | |
| seller_covers_fees | No | If 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_subscription | No | If 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_override | No | Optional. Override the estimated eBay final value fee percentage (e.g. for a seller with an eBay Store subscription). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses behavioral traits: calculations are deterministic using dated fee schedules, competitor marketplaces off by default, only fixed-price seller fees modeled, and advice to present figures as estimates without claiming universal cheapest. This provides clear expectations for the agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured paragraph with front-loaded purpose. Every sentence adds value: use cases, exclusions, behavioral notes, and presentation guidance. No redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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, the description covers all needed context: what the tool does, when to use it, limitations, parameter grouping, and behavioral assumptions. It is complete enough for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds significant context beyond parameter descriptions, such as explaining defaults for methods, the meaning of seller_plan tiers, and the nuance of seller_covers_fees. It helps the agent understand parameter interactions, justifying above baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 seller proceeds across multiple selling methods for trading cards. It specifies the verb (compare), resource (seller proceeds), and scope (trading cards). It also explicitly distinguishes from tools that price cards or cover non-trading-card categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use scenarios (e.g., 'when a seller asks what they would keep/net/take-home') and when-not-to-use (do not use for pricing cards or non-trading-card categories). It also explains that competitor marketplaces are off by default and that only fixed-price fees are modeled.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!