Resollo Agent API

Get Resollo product details

products.get

Read-only

Fetch the full details of one specific Resollo product listing by its ID, including its Semantic Profile (suitable_for, not_ideal_for, target_audience, key_strengths, evokes, is_similar_to -- useful for judging fit against a buyer's stated needs), attributes, all image URLs, shipment prices, and the seller's accepted payment/shipment methods. Returns not_found for products that don't exist, are sold, expired, or moderation-hidden. No authentication required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	No	ISO 4217 code for the returned price fields. Defaults to USD. Same semantics as in search_products.
`productId`	Yes	The product listing's uuid.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`name`	Yes
`unit`	Yes
`price`	Yes
`seller`	Yes
`category`	Yes
`condition`	Yes
`guarantee`	Yes
`image_url`	Yes
`min_price`	Yes
`attributes`	Yes
`created_at`	Yes
`image_urls`	Yes
`description`	Yes
`listing_type`	Yes
`offers_enabled`	Yes
`auction_ends_at`	Yes
`converted_price`	Yes
`shipment_prices`	Yes
`semantic_profile`	Yes
`quantity_available`	Yes

TDQS

A4.4/5.0

Behavior5/5

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

It discloses no-authentication-requirement, and the not_found cases (nonexistent, sold, expired, moderation-hidden) go well beyond the readOnlyHint annotation. These are the behavioral nuances an agent needs to interpret responses correctly.

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?

The description is dense but efficient, front-loading the core action and resource. The parenthetical definition of the Semantic Profile is a bit verbose, yet it directly aids tool selection by telling the agent why that data matters for buyer fit.

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?

Given the tool has an output schema, full parameter schema coverage, and readOnly annotations, the description supplies the remaining essential context: no authentication, not_found semantics, and the key returned areas. Nothing critical to correctly invoking or interpreting this tool is missing.

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 description coverage is 100%, so both productId and currency are already fully documented in the schema. The description adds no parameter-level meaning beyond the schema, which aligns with the baseline for full schema coverage.

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 uses a specific verb ('Fetch') and resource ('product listing by ID'), and enumerates the returned fields, making it unmistakably distinct from the sibling search tool products.search. It also highlights the Semantic Profile as a key differentiator for buyer-fit evaluation.

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

Usage Guidelines4/5

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

The description makes clear this is the tool for retrieving a single product's full details by ID and notes not_found behavior. It does not explicitly name alternatives or state when not to use it, but the context strongly implies it for exact product lookups rather than discovery.

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

All Resollo Agent API tools Inspect

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.4/5.0

Disambiguation5/5

Each tool targets a distinct resource and action (marketplace metadata, offers, orders, products, questions, reviews, sellers), so an agent can reliably select the right one. The few same-domain tools (products.get/search, sellers.get/status) are clearly separated by their descriptions.

Naming Consistency4/5

Names mostly follow a clear domain.action pattern (products.create, questions.ask, orders.place), with domain prefixes making the surface predictable. Minor deviations like orders.checkoutLink (camelCase) and noun-style endpoints (marketplace.info, orders.status, sellers.status) keep it from being fully uniform.

Tool Count5/5

Fifteen tools is a well-scoped size for a marketplace API; each tool supports a distinct part of browsing, buying, selling, or marketplace reference data. No obvious redundant tools or bloated surface.

Completeness3/5

The tool set covers a wide marketplace workflow, but there are notable gaps: no endpoint to list the authenticated user's own orders, offers, or listings, and no product update/delete/activate after draft creation. Agents can work around some gaps via returned IDs and manual web steps, but certain user requests will dead-end.

Resources

Need Help?