Skip to main content
Glama
SocialAPIsHub

SocialAPIs MCP Server

Official

facebook_marketplace_rentals

Filter Facebook Marketplace rental listings by bedrooms, bathrooms, location, and price to discover properties.

Instructions

Search Marketplace rental property listings with filters for bedrooms, bathrooms, location, price

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_byNoSort: CREATION_TIME_DESCEND, PRICE_ASCEND, BEST_MATCH
filter_location_latitudeNoGPS latitude
filter_location_longitudeNoGPS longitude
filter_price_lower_boundNoMinimum price
filter_price_upper_boundNoMaximum price
filter_radius_kmNoRadius in km
filter_bedrooms_minNoMin bedrooms
filter_bedrooms_maxNoMax bedrooms
filter_bathrooms_minNoMin bathrooms
filter_bathrooms_maxNoMax bathrooms
end_cursorNoPagination cursor
Behavior2/5

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

No annotations exist, so description must fully disclose behavior. It only states 'search' but omits pagination, default sorting, result structure, or API limits. Parameter 'end_cursor' hints at pagination but is unmentioned in description.

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?

Single sentence, no waste. However, could benefit from brevity with additional structuring details (e.g., list of filter types). Currently concise but borderline under-specified.

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?

11 parameters, no output schema, and many sibling tools require rich context. Description fails to explain pagination, required vs optional filters, or result format. Lacks enough detail for effective use.

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 covers 100% of parameters with descriptions. Description adds phrase 'with filters for bedrooms, bathrooms, location, price', which groups parameters but does not add meaningful semantics beyond schema.

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?

Description explicitly states 'Search Marketplace rental property listings with filters', clearly indicating the tool's purpose for rental-specific search, distinguishing it from sibling tools like facebook_marketplace_vehicles and facebook_marketplace_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. alternatives. With many sibling marketplace tools, the description should clarify why to choose rentals over general search or vehicles, but provides no such context.

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/SocialAPIsHub/mcp-server'

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