Skip to main content
Glama

Get marketplace seller

get_marketplace_seller
Read-onlyIdempotent

Marketplace seller profile by id (from a marketplace listing's seller): display name, verification and trust badges, ratings and reputation, plus their active offers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sellerId": "<sellerId>"
    },
    "name": "get_marketplace_seller"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerIdYesSeller public id, e.g. usr_Fz1bpXt90L9Y.
includeListingsNoInclude the seller's active marketplace listings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the returned field categories but no extra behavioral context such as auth requirements or how includeListings interacts with the returned offers.

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?

A single compact sentence with the resource and its key fields front-loaded; every element is relevant. Slightly dense but no wasted filler.

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?

With no output schema, the description carries the burden of describing return values and does so by listing the field categories. It is complete enough for an agent to call the tool correctly, though it omits error/empty-result behavior.

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 parameters (sellerId format example and includeListings default) are already fully documented in the schema. The description's mention of 'active offers' only loosely maps to includeListings and adds no syntax or format detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Marketplace seller profile by id') and enumerates the returned content (display name, verification and trust badges, ratings, offers). It does not explicitly contrast with the closely related sibling get_marketplace_listing_details, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(from a marketplace listing's seller)' tells the agent where the id originates, but there is no explicit when-to-use or when-to-prefer-an-alternative guidance. Adequate but with a clear gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.