Skip to main content
Glama

search_marketplace

Find items for sale across Kijiji, Craigslist, and Facebook Marketplace using a single search with location, category, and price filters.

Instructions

Search Kijiji, Craigslist, and Facebook Marketplace simultaneously. Takes human-readable parameters (city name, category, price range) and returns grouped results from all platforms. Use fetch(url) to get full listing details for any result URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort orderdate
queryYesSearch keywords (e.g. "golf r", "ikea couch")
categoryNoCategory filterall
locationYesCity name, optionally with province/state (e.g. "toronto", "st catharines, ON", "seattle")
conditionNoItem condition filter
max_priceNoMaximum price in dollars
min_priceNoMinimum price in dollars
platformsNoPlatforms to search (default: all). Kijiji is Canada-only and auto-skipped for US locations.
Behavior3/5

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

With no annotations, the description bears full burden. It mentions 'grouped results' and simultaneous search, but omits details on rate limits, authentication, error handling, or result volume.

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?

Three sentences, immediately stating the main purpose and key features. No redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 8 parameters and no output schema, the description is very brief. It does not explain return format, pagination, error behavior, or how to interpret grouped results.

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 the description adds minimal value beyond what schema already provides. It restates 'human-readable parameters' but doesn't elaborate on format or constraints.

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 clearly states the verb 'Search' and the specific resources (Kijiji, Craigslist, Facebook Marketplace), distinguishing it from sibling tools like search_aliexpress or search_reddit.

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?

The description implies usage for multi-platform searches, but lacks explicit guidance on when not to use it or how it compares to alternatives like the 'fetch' tool for individual listings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Averyy/fetchaller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server