Skip to main content
Glama

facebook_marketplace_location_search

Disambiguate city names into Marketplace hubs — id + lat/lng. Flat 2 credits. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "facebook_marketplace_location_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCity/place query. Bare names like 'Austin' may return multiple candidates (TX/MN/IN); include a state for a single hit (e.g. 'Austin, TX').
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 10, max 50). Flat 2 credits per call.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  4. Changed3 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 50. Flat 2 credits per call."New value: +"Max items to return (default 10, max 50). Flat 2 credits per call."
    • changedInput schema / properties / q / description
      Previous value: -"City/place query. Bare 'Austin' may return TX/MN/IN; include a state for a single hit."New value: +"City/place query. Bare names like 'Austin' may return multiple candidates (TX/MN/IN); include a state for a single hit (e.g. 'Austin, TX')."
  5. Changed3 schema fields changed
    • removedInput schema / properties / details
      Removed value: -{
      -  "description": "Set true to include latitude/longitude per location (slower; doubles cost to 34 credits).",
      -  "type": "string"
      -}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 50. Flat 17 credits per call."New value: +"Max items to return. Default 10, max 50. Flat 2 credits per call."
    • changedInput schema / properties / q / description
      Previous value: -"City/place search query, e.g. Austin."New value: +"City/place query. Bare 'Austin' may return TX/MN/IN; include a state for a single hit."
  6. Changed2 schema fields changed
    • changedInput schema / properties / details / description
      Previous value: -"Set true to include latitude/longitude per location (slower; doubles cost to 2 credits)."New value: +"Set true to include latitude/longitude per location (slower; doubles cost to 34 credits)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 50. Flat 2 credits per call."New value: +"Max items to return. Default 10, max 50. Flat 17 credits per call."
  7. Changed2 schema fields changed
    • changedInput schema / properties / details / description
      Previous value: -"Set true to include latitude/longitude per location (slower; doubles cost to 34 credits)."New value: +"Set true to include latitude/longitude per location (slower; doubles cost to 2 credits)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 50. Flat 17 credits per call."New value: +"Max items to return. Default 10, max 50. Flat 2 credits per call."
  8. Changed1 schema field changed
    • addedInput schema / properties / details
      Added value: +{
      +  "description": "Set true to include latitude/longitude per location (slower; doubles cost to 34 credits).",
      +  "type": "string"
      +}
  9. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 50. Billed per result."New value: +"Max items to return. Default 10, max 50. Flat 17 credits per call."
  10. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  11. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  12. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description usefully discloses that calls cost 'Flat 2 credits', that 'Empty results and failures are never charged', and that cache=true can yield a free 24h cache hit while the default is fresh. These are meaningful behavioral details beyond the schema, though read-only status, auth requirements, and rate limits are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and output shape are front-loaded, and the cache/billing notes are useful. However, 'Flat 2 credits. Costs 2 credits.' is redundant, so not every sentence earns its place.

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 simple location-resolution tool with 5 fully described parameters and no output schema, the description covers purpose, output shape, cost, caching, and billing failures. It is largely complete, though it could better connect this step to the Marketplace listing-search tools.

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%, and the schema already explains q disambiguation, cache behavior, limit, fields, and compact. The description reinforces cache=true as a free 24h cache hit, but adds little parameter meaning beyond what the schema already provides, 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?

The description gives a specific verb and resource: 'Disambiguate city names into Marketplace hubs', and states the useful output shape as 'id + lat/lng'. It is clearly distinct from listing-search siblings in substance, but it does not explicitly name an alternative or state when not to use it.

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 phrase 'Disambiguate city names into Marketplace hubs', so an agent can infer this is a location-resolution step. However, there is no explicit when-to-use guidance relative to facebook_marketplace_search or other siblings, and no stated prerequisites or exclusions.

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.