Skip to main content
Glama

NeuralVerge Business Intelligence

Craigslist Postings Search

run_craigslist_postings_search

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

TableJSON 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. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses the per-record cost ('1 point per returned record') and enumerates the returned fields, compensating for the absent output schema. It stops short of describing pagination limits beyond what max_items/start_page imply.

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-loaded with the verb and scope, then compactly groups the 60+ filters into a single readable list before noting the cost. No filler, and it fits a very large schema in two sentences.

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 67-parameter tool with no annotations and no output schema, the description covers purpose, filter breadth, return fields, and cost. The one notable gap is guidance on choosing the required 'area' value (a sibling like run_craigslist_areas exists for that) and pagination behavior.

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 every one of the 67 parameters is documented in the schema itself. The description's summary of filter groups (vehicle, motorcycle, boat, housing, job, gig, event) adds little beyond what the schema already names, 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 (Search) and resource (live Craigslist postings) with scope (any regional site) and the filter categories covered. It clearly reads as the search tool among the Craigslist siblings, though it never explicitly names run_craigslist_postings or run_craigslist_postings_seller to disambiguate.

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 phrasing implies usage (search live postings, in any regional site) but gives no explicit when-to-use vs. the retrieval-by-ID sibling, no prerequisites, and no exclusions. Usage is inferable rather than stated.

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