Skip to main content
Glama
Sign In

Aura Historia MCP

by com.aura-historia.mcp
OverviewDiscussionsAdmin

Get listing

getProductListing
Read-onlyIdempotent

Get the full details of one listing by its productListingId: text, prices, images, provider, availability, auction and shipping, in the requested language and currency. Use it when the user wants more than a search result shows. For a signed-in user, each result also carries userState sections for which the token has the read scope: watchlist:read, search-filters:read, notifications:read or users:read.

Input Schema

NameRequiredDescriptionDefault
currencyNoEUR
languageNoen
productListingIdYes

Output Schema

NameRequiredDescriptionDefault
itemYes
userStateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / $defs / AuctionScheduleData / required
      Removed value: -[
-  "biddingOpens",
-  "liveStarts",
-  "lotsBeginClosing",
-  "scheduledEnd"
-]
    • addedOutput schema / $defs / ListingTextData
      Added value: +{
+  "description": "A listing text as the source published it and as shown for the requested language.",
+  "properties": {
+    "localized": {
+      "$ref": "#/$defs/LocalizedTextData",
+      "description": "Text to show for the requested language. Chosen from the translations and the original in\nthe order requested language, `en`, `de`, then any other language, so it can be the\noriginal itself. Always present; compare its `language` with `original.language` to tell\nwhether the text was translated."
+    },
+    "original": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/LocalizedTextData"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Text as the source published it, normalized: styled letters and digits are presented as\nordinary text, emoji and ornamental symbols are removed and truncation ellipses remain\nstable. Omitted where the response does not carry the original, such as search and\nsimilar-listing summaries and notification payloads."
+    }
+  },
+  "required": [
+    "localized"
+  ],
+  "type": "object"
+}
    • changedOutput schema / $defs / ProductListingDetailsData / properties / description / anyOf
      Previous value: -[
-  {
-    "$ref": "#/$defs/LocalizedTextData"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/ListingTextData"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / $defs / ProductListingDetailsData / properties / productDescription
      Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/LocalizedTextData"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / $defs / ProductListingDetailsData / properties / productTitle
      Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/LocalizedTextData"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • changedOutput schema / $defs / ProductListingDetailsData / properties / title / anyOf
      Previous value: -[
-  {
-    "$ref": "#/$defs/LocalizedTextData"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/ListingTextData"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / ProductListingDetailsData / required
      Previous value: -[
-  "productListingId",
-  "eventId",
-  "source",
-  "sourceListingId",
-  "pricing",
-  "availability",
-  "lifecycle",
-  "url",
-  "viewUrl",
-  "images",
-  "contentPolicy",
-  "auction",
-  "lot",
-  "created",
-  "updated"
-]New value: +[
+  "productListingId",
+  "eventId",
+  "source",
+  "sourceListingId",
+  "pricing",
+  "lifecycle",
+  "url",
+  "viewUrl",
+  "images",
+  "created",
+  "updated"
+]
    • removedOutput schema / $defs / ProductListingImageData / required
      Removed value: -[
-  "url"
-]
    • removedOutput schema / $defs / ProductListingLotData / required
      Removed value: -[
-  "lotNumber",
-  "cataloguePosition",
-  "biddingOpens",
-  "scheduledCloses",
-  "reportedClosedAt"
-]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: language and currency shape the returned payload, and the userState sections returned depend on which token scopes (watchlist:read, search-filters:read, notifications:read, users:read) the caller holds. It does not describe behavior for an unknown or malformed productListingId.

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?

Two sentences, front-loaded with the core action and returned fields, then the usage trigger, then the conditional userState detail. No filler or restated name/title.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still summarizes the payload shape and the auth-scope-dependent extras. What remains thin is the identifier contract (validity, not-found behavior) and default language/currency application, both of which an agent might want before calling.

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 0%, so the description must carry the parameter meaning; it does so only for language and currency ("in the requested language and currency"), noting they localize the response. productListingId is mentioned only as the lookup key, with its format/pattern left entirely to the schema, and default values are unmentioned. Partial compensation for the coverage gap.

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 ("Get the full details of one listing by its productListingId") and enumerates the returned facets: text, prices, images, provider, availability, auction, shipping. The phrase "more than a search result shows" implicitly separates it from simpleSearchProductListings and getSimilarProductListings.

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?

"Use it when the user wants more than a search result shows" gives a clear selection condition against the search siblings. It stops short of naming explicit alternatives (getProductListingByTitleSlug, getSimilarProductListings, getAuction) or stating when not to use it, so no exclusion is spelled out.

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

All Aura Historia MCP 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