Skip to main content
Glama
jlsookiki

Secondhand MCP

by jlsookiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_listing_details

Read-onlyIdempotent

Fetch full listing details by ID: description, photos, location, seller, and shipping options. Control photo delivery via URLs or inline base64 to work around CDN blocks.

Instructions

Get one listing in full using an id from search_marketplace or from a marketplace URL: description, every photo, location, seller and shipping options. Photos: by default (imageMode:"urls") you get direct full-resolution CDN image URLs to fetch yourself, which is the most reliable option because some CDNs block server-side fetches. Set imageMode:"inline" (or includeImages:true) to have the server fetch the photos and return them as base64 image blocks; if that fetch is blocked the server falls back to URLs. Use imageSize to trade resolution for payload and maxImages to cap the count. Requirements: the same as search_marketplace for that marketplace. Behavior: read-only, one listing per call, no login. Errors: a listing that has been removed, or an id from the wrong marketplace, returns an error message rather than a partial listing. Not for: searching (use search_marketplace) or fetching many listings at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageModeNoHow photos are returned. "urls" (default): direct full-resolution CDN image URLs for you to fetch yourself — most reliable, bypasses CDN blocking of server-side fetches, defaults to full resolution. "inline": server fetches every photo and returns them as base64 image blocks in this one call; if the server fetch is blocked it automatically falls back to returning the URLs.urls
imageSizeNoResolution for eBay images: thumb (~400px), standard (~800px), full (~1600px). Defaults to full for imageMode "urls" and standard for "inline". Non-eBay images are returned as-is.
listingIdYesThe listing ID (from search results or a marketplace URL)
maxImagesNoCap the number of photos returned (default: all). Use to keep the response small for listings with many photos.
marketplaceNoWhich marketplace the listing is from (default: facebook)facebook
includeImagesNoDeprecated alias for imageMode:"inline". If true and imageMode is unset, photos are fetched server-side and returned inline as base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.1
    • addedInput schema / properties / imageMode
      Added value: +{
+  "default": "urls",
+  "description": "How photos are returned. \"urls\" (default): direct full-resolution CDN image URLs for you to fetch yourself — most reliable, bypasses CDN blocking of server-side fetches, defaults to full resolution. \"inline\": server fetches every photo and returns them as base64 image blocks in this one call; if the server fetch is blocked it automatically falls back to returning the URLs.",
+  "enum": [
+    "urls",
+    "inline"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / imageSize
      Added value: +{
+  "description": "Resolution for eBay images: thumb (~400px), standard (~800px), full (~1600px). Defaults to full for imageMode \"urls\" and standard for \"inline\". Non-eBay images are returned as-is.",
+  "enum": [
+    "thumb",
+    "standard",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / includeImages / description
      Previous value: -"Return actual image content instead of URLs. Images are returned as base64-encoded content blocks that the model can see."New value: +"Deprecated alias for imageMode:\"inline\". If true and imageMode is unset, photos are fetched server-side and returned inline as base64."
    • addedInput schema / properties / maxImages
      Added value: +{
+  "description": "Cap the number of photos returned (default: all). Use to keep the response small for listings with many photos.",
+  "type": "number"
+}
  2. First observedv0.4.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond those: one listing per call, no login required, photo fetch/fallback behavior, and concrete error behavior for removed listings or wrong-marketplace IDs. This exceeds what annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is dense but well organized: the core purpose is front-loaded, the photo-mode behavior is explained in compact conditional terms, and the constraints/errors/not-for guidance are each one clear sentence. No sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description tells the agent what fields will appear, how photos behave in both modes, how to cap payload, what requirements apply, what errors look like, and what the tool is not for. This is complete enough for correct invocation and expectation-setting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, and the description additionally explains the semantic difference between imageMode values, the automatic fallback from inline to URLs, the resolution tradeoff of imageSize, maxImages as a payload cap, and the includeImages alias. This adds substantial meaning beyond the schema definitions.

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 states a specific verb ('Get'), a specific resource ('one listing in full'), and the source of the ID ('search_marketplace or a marketplace URL'). It lists the returned content and explicitly distinguishes itself from searching and batch fetching, making it clearly different from its siblings.

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?

The description gives explicit when-to-use guidance: retrieve one full listing by ID. It names alternatives for what it is not for — 'search_marketplace' for searching and no batch operation for many listings — and even notes the same requirements as search_marketplace apply.

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

Deploy Server

Other Tools