Skip to main content
Glama

run_craigslist_postings_search

Search live Craigslist postings by keyword, category, area, and filters like price, housing, jobs, vehicles, or events, returning titles, prices, dates, locations, and images.

Instructions

Search live Craigslist postings in any regional site by keyword, category, area/sub-area/postal/coordinates and 60+ vehicle, motorcycle, boat, housing, job, gig and event filters; returns title, price, date, location, images and category facets. 1 point per returned record.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude
lonNoLongitude
areaYesArea. e.g. sfbay
freeNoFree items only
sortNoSort by. Options: oldest = Oldest, price_asc = Price: low to high, price_desc = Price: high to low, distance = Distance, relevance = Relevance, upcoming = Upcoming
paintNoPaint color
postalNoPostal code. e.g. 94103
radiusNoRadius (miles)
is_paidNoGig pay. Options: all = All, paid = Paid, unpaid = Unpaid
keywordNoSearch term (optional). e.g. bike
laundryNoLaundry
parkingNoParking
subareaNoSub-area. e.g. sfc
categoryNoCategory (optional). e.g. sss
languageNoPosting language
max_sqftNoArea, sq ft (max)
min_sqftNoArea, sq ft (min)
purveyorNoSold by. Options: all = All, owner = Owner, dealer = Dealer
boat_typeNoBoat type
body_typeNoBody type
conditionNoCondition
crypto_okNoCrypto accepted
cylindersNoCylinders
fuel_typeNoFuel
has_imageNoHas image
max_itemsNoMax items (up to 500)
max_priceNoPrice (max)
min_priceNoPrice (min)
drivetrainNoDrivetrain
make_modelNoMake and model. e.g. honda civic
start_pageNoStarting page
event_typesNoEvent types
rent_periodNoRent period
titles_onlyNoSearch titles only
availabilityNoMove-in availability. Options: all = All dates, within_30_days = Within 30 days, beyond_30_days = Beyond 30 days
housing_typeNoHousing type
is_nonprofitNoNon-profit employers only
max_bedroomsNoBedrooms (max)
min_bedroomsNoBedrooms (min)
posted_todayNoPosted today
street_legalNoStreet legal only
title_statusNoTitle status
transmissionNoTransmission
is_internshipNoInternships only
lost_or_foundNoLost or found
max_auto_yearNoModel year (max)
max_bathroomsNoBathrooms (max)
min_auto_yearNoModel year (min)
min_bathroomsNoBathrooms (min)
max_auto_milesNoOdometer (max)
min_auto_milesNoOdometer (min)
boat_propulsionNoPropulsion
employment_typeNoEmployment type
hide_duplicatesNoHide duplicates
max_boat_lengthNoLength overall (max)
min_boat_lengthNoLength overall (min)
motorcycle_typeNoType
housing_featuresNoRequired features
is_telecommutingNoTelecommuting allowed
motorcycle_motorNoMotor
delivery_availableNoDelivery available
max_monthly_paymentNoMonthly payment (max)
min_monthly_paymentNoMonthly payment (min)
max_year_manufacturedNoYear manufactured (max)
min_year_manufacturedNoYear manufactured (min)
max_engine_displacement_ccNoEngine displacement, cc (max)
min_engine_displacement_ccNoEngine displacement, cc (min)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the returned fields (title, price, date, location, images, facets) and the cost model (1 point per returned record), but omits pagination behavior, rate limits, and auth requirements.

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, front-loaded with the verb+resource, followed by return fields and cost. Appropriately sized for a tool with 67 parameters with no wasted prose.

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?

No output schema and no annotations exist, so the description must carry returns and behavior. It covers the returned record shape and the cost model well; the main uncoved gaps (pagination, rate limits, auth) are relatively minor against a fully-described schema.

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 the field-level meaning is already documented. The description adds a small amount of meaning by grouping the 67 parameters into coherent filter families (vehicle, motorcycle, boat, housing, job, gig, event) and locator modes, but not enough to exceed the baseline.

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?

The description states a specific verb (Search) and resource (live Craigslist postings) and defines the scope (any regional site) plus the breadth of filters and returned fields. It's clear and informative, though it doesn't explicitly name or distinguish itself from the very similar sibling run_craigslist_postings.

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 implied: search postings by keyword/category/area or by the dozens of domain filters. There is no explicit when-to-use vs when-not guidance, no naming of an alternative sibling, and no prerequisites, so an agent must infer fitness from context.

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

Deploy Server

Other Tools