Skip to main content
Glama

Search marketplace listings

search_marketplace_listings
Read-onlyIdempotent

Search the VanAuto marketplace (akcesoria - camper parts and accessories). Supports text, manufacturer, category, condition, compatibility and price filters. Returns compact rows plus facets with category/condition counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_marketplace_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based).
queryNoFree-text search over title and description.
perPageNoRows per page (1-50).
categoryNoCategory slug, e.g. "appliances", "plumbing_water".
locationNoCity name or postal code text filter.
priceMaxNoMaximum price in PLN.
priceMinNoMinimum price in PLN.
conditionNoItem condition.
subcategoryNoSubcategory slug, e.g. "toilets", "refrigeration".
manufacturerNoManufacturer/brand text filter.
compatibilityNoCamper compatibility tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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/idempotence profile is covered. The description adds the return shape ("compact rows plus facets with category/condition counts"), which is genuinely useful given no output schema, but says nothing about pagination limits or result caps.

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?

Two sentences with no filler; the resource and scope come first and the return-shape detail second. Slightly denser than ideal but every clause carries information.

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?

For a read-only search tool with no output schema, the description covers the domain scope and the return shape (rows plus facets). The main gap is pagination/limit behavior and how the filters combine (AND vs OR), which an agent might need.

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%, so every parameter is already documented in the schema. The description groups the filters (text, manufacturer, category, condition, compatibility, price) at a high level but adds no syntax, format or example detail beyond what the schema provides, so the baseline 3 applies.

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 ("Search the VanAuto marketplace") and scopes it to camper parts and accessories. This implicitly distinguishes it from siblings like search_campers and search_wanted_ads, but the differentiation is not stated explicitly, 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 Guidelines2/5

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

The description enumerates supported filters but never states when to use this tool versus alternatives such as get_marketplace_listing_details or search_campers. No when/when-not conditions are given, leaving routing to inference.

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.