Skip to main content
Glama

Current Craigslist listings for one site and category

ecommerce_craigslist
Read-only

Current Craigslist listings for one site and category (e.g. sfbay + cta = cars & trucks, newyork + apa = apartments), optionally matching a search query: title, price, area and listing URL, newest first as Craigslist orders them, read from the public search page. Up to ~300 results per call; no contact details or full post text. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "site": "<site>"
    },
    "name": "ecommerce_craigslist"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesCraigslist site subdomain, e.g. sfbay, newyork, losangeles, london (required)
limitNoListings to return, 1 to 300 (default 25)
queryNoSearch words (optional)
categoryNoCategory code, e.g. sss (all for sale), cta (cars+trucks), apa (apartments), jjj (jobs), bik (bikes). Default sss

Output Schema

NameRequiredDescriptionDefault
siteNo
countNo
queryNo
totalNo
sourceNo
categoryNo
listingsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the readOnlyHint/openWorldHint annotations: ordering (newest first as Craigslist orders them), a per-call ceiling (~300 results), explicit exclusions (no contact details, no full post text), and data provenance from the public search page. It also discloses billing (charged only on success, x402 USDC), which is valuable operational context. Minor gap: no pagination or rate-limit behavior stated.

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?

Front-loads the purpose, then fields/ordering, then limits and price - logical order with no filler. The single long compound sentence is dense but each clause carries information the agent needs.

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 an output schema present, the description need not document return values, yet it still names the returned fields and their ordering. Combined with a fully documented 4-parameter schema and annotations, the definition is essentially complete; only deep pagination semantics are absent.

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 site, limit, query and category are already documented, including example codes. The description's site+category examples and its "~300" ceiling largely restate the schema, adding only the relationship between site and category via a combined example.

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 ("Current Craigslist listings for one site and category") and pins the scope with concrete site+category examples (sfbay + cta, newyork + apa). An agent can tell this is a scoped listing/search tool rather than a general web fetch.

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?

Makes clear this is a public search-page read of current listings, optionally narrowed by a search query, so the agent knows the intended context. It does not name any alternative tool or when-not-to-use condition, but that is less critical here given the narrow resource.

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.

Resources