Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

Search Facebook Marketplace listings

facebook_marketplace_search_list
Read-only

Search Facebook Marketplace listings by keyword near a latitude and longitude. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude for the marketplace search location.
lngNoLongitude for the marketplace search location.
countNoDeprecated alias for `limit`. When both are set, `limit` wins.
limitNoOptional number of listings to return (1–100). Prefer this over `count`.
queryYesSearch query text for marketplace listings.
cursorNoOpaque pagination cursor returned by a previous response.
sortByNoOptional sort order for marketplace listings. `suggested`: Facebook's default relevance ranking. `distanceAscend`: nearest first. `creationTimeDescend`: newest listings first. `priceAscend`/`priceDescend`: lowest/highest price first.
maxPriceNoOptional maximum listing price. Must be greater than or equal to `minPrice` when both are set.
minPriceNoOptional minimum listing price. Must be less than or equal to `maxPrice` when both are set.
radiusKmNoOptional search radius in kilometers.
conditionNoOptional item condition filter for marketplace listings.
dateListedNoOptional date-listed filter for marketplace listings. `1`/`last24Hours` both mean the last 24 hours, `7`/`last7Days` both mean the last 7 days, and `30`/`last30Days` both mean the last 30 days — these are separate values Facebook accepts for the same window; prefer the named variants (`last24Hours`, `last7Days`, `last30Days`) for clarity. `all` applies no date filter.
availabilityNoOptional availability filter for marketplace listings.
deliveryMethodNoOptional delivery method filter for marketplace listings.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds practical behavior on pagination ('use cursor when paginated'), which goes beyond annotations. It does not contradict annotations. The lack of depth (e.g., rate limits, response format) is mitigated by the annotations.

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?

The description is two sentences with no fluff, front-loading the core purpose and adding a pagination tip. It is concise but not overly sparse, efficiently conveying the essential behavior.

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?

Given 14 parameters and no output schema, the description only covers keyword and location, omitting the extensive filter options (price, condition, sort, etc.) that are documented in the schema. An agent might not realize these capabilities are available. The pagination tip is helpful, but the description does not convey the tool's full expected behavior or return structure beyond 'a list'.

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 schema already documents all parameters with detailed descriptions. The description does not add additional meaning beyond what the schema provides; it only reinforces the role of query/lat/lng. This meets the baseline of 3 for high schema coverage.

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?

The description clearly states the action ('Search'), resource ('Facebook Marketplace listings'), and key parameters ('by keyword near a latitude and longitude'), making it easy to distinguish from siblings like facebook_marketplace_item_get (single item) and facebook_marketplace_locations_search (locations). The purpose is specific and unambiguous.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where another sibling tool would be more appropriate. For a search tool with many sibling marketplace tools, this is a notable gap.

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

All Social Fetch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources