Skip to main content
Glama

Craigslist Postings Search

run_craigslist_postings_search
Read-onlyIdempotent

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) Default: 25.
max_priceNoPrice (max)
min_priceNoPrice (min)
drivetrainNoDrivetrain
make_modelNoMake and model. e.g. honda civic
start_pageNoStarting page Default: 1.
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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds two non-annotation facts: results are 'live' (real-time sourcing) and each returned record costs 1 point, a metering detail the agent needs before calling.

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 and resource, that stay compact despite covering a 67-parameter tool. It is dense but every clause (filters, return fields, cost) 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 high-complexity tool with 67 params and no output schema, the description usefully names the returned fields (title, price, date, location, images, facets) and the cost model. Pagination controls (start_page, max_items) are left to the schema, which is acceptable but is the main residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a filter taxonomy that the schema does not express: it groups the 60+ filters into vehicle/motorcycle/boat/housing/job/gig/event families and names the geo inputs (area/sub-area/postal/coordinates). This helps an agent reason about which parameter family to reach for.

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 ('Search') and resource ('live Craigslist postings') and enumerates the scope of what can be searched (keyword, category, geo, 60+ filters). It also lists return fields. It does not explicitly distinguish itself from sibling run_craigslist_postings or run_craigslist_postings_seller, so it stops 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 implied by the name and the 'any regional site' framing, and the billing note ('1 point per returned record') is a useful cost signal for deciding to call it. However, there is no explicit when-to-use/when-not guidance or named alternative sibling (e.g., postings lookup vs. seller postings).

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.