Skip to main content
Glama

Resollo Agent API

by com.resollo
OverviewDiscussionsAdmin

List the authenticated seller's own listings (any state)

sellers.listings
Read-only

Returns the caller's own product listings in EVERY state -- active, inactive, pending moderation, rejected, and closed -- not just the publicly visible ones (soft-deleted listings are excluded). Use this to find a draft created earlier with products.create (those sit in state 'inactive' until the seller activates them) when you no longer have its product_id, or to review what the seller currently has listed. Each entry includes the listing's state, category, condition, price, quantity, and an edit_url (the seller's product page where an inactive draft is reviewed and activated). A products.create draft's price is the midpoint of Resollo's AI price suggestion; the seller can change it before activating. Optionally filter to a single state. Read-only, no side effects. Requires a signed-in Resollo user (OAuth sign-in, or an 'Authorization: Bearer ' header).

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of most-recent listings to return (1-100, default 50).
stateNoOptional filter to a single listing state. 'inactive' is where products.create drafts sit until the seller activates them. When omitted, listings in every state are returned.

Output Schema

NameRequiredDescriptionDefault
countYes
listingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / listings / items / properties / created_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / listings / items / properties / created_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / listings / items / properties / updated_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / listings / items / properties / updated_at / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / listings / items / properties / category
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "type": "number"
+    },
+    "key": {
+      "type": "string"
+    },
+    "name_en": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "key",
+    "name_en"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / listings / items / properties / condition
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "key": {
+      "type": "string"
+    },
+    "name_en": {
+      "type": "string"
+    },
+    "value": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "key",
+    "name_en"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / listings / items / required
      Previous value: -[
-  "id",
-  "name",
-  "state",
-  "state_flags",
-  "listing_type",
-  "price",
-  "quantity",
-  "offers_enabled",
-  "edit_url",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "id",
+  "name",
+  "state",
+  "state_flags",
+  "listing_type",
+  "category",
+  "condition",
+  "price",
+  "quantity",
+  "offers_enabled",
+  "edit_url",
+  "created_at",
+  "updated_at"
+]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the 'Read-only, no side effects' line is redundant, but the description still earns credit by disclosing that soft-deleted listings are excluded and spelling out the auth requirement (OAuth sign-in or Bearer agent API key header). It also explains the lifecycle semantics of 'inactive' drafts and where edit_url points.

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 most important fact — all states, not just public ones — is front-loaded, and each sentence is informational. It runs long, though, and the aside about drafts carrying the midpoint of Resollo's AI price suggestion is tangential to selecting or invoking the tool.

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?

Everything an agent needs to choose and call this tool is present: state coverage, the draft-recovery use case, auth prerequisites, exclusion of soft-deleted items, and optional filtering. Return values are already covered by the output schema, and the description's field summary is a bonus rather than a requirement.

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% and both parameters are fully documented there, including the state enum and limit bounds, so baseline 3 applies. The description restates 'optionally filter to a single state' and the meaning of 'inactive' without adding anything the schema does not already say, and it never mentions 'limit'.

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?

States a specific verb and resource ('Returns the caller's own product listings') and pins down the scope precisely: every state including inactive, pending_moderation, rejected, closed, excluding soft-deleted. This distinguishes it cleanly from public-search siblings like products.search and from products.get / products.create.

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?

Gives two explicit usage triggers: recovering a draft created with products.create when the product_id is lost, and reviewing what the seller currently has listed. It implicitly excludes public-facing search ('not just the publicly visible ones') but never names products.search or products.get as the alternative for that case.

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 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