Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

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).

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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')."
  3. 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."
  4. 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."
  5. 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."
  6. 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"
+}
  7. 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."
  8. 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."
  9. 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"
+}
  10. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral disclosure burden. It explicitly states the flat 2-credit cost, that empty results and failures are never charged, and the cache semantics (cache=true gives a free 24h hit, default is always fresh). These are the key behavioral traits an agent needs to make cost-aware decisions, and they are communicated clearly.

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 short and front-loads the purpose and output. However, it contains a redundant duplicate: 'Flat 2 credits. Costs 2 credits.' — the same fact stated twice in adjacent fragments. Otherwise every sentence earns its place, covering output, cost, failure pricing, and cache behavior.

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 3-parameter tool with no output schema, the description covers purpose, cost, caching, and a partial output shape (id + lat/lng). It is complete enough for an agent to call the tool correctly. It could be stronger by describing the response structure in more detail, but the minimal output hint is sufficient for this use case.

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 baseline is 3. The description adds no new parameter meaning beyond the schema: it repeats the cache cost/behavior already documented in the schema and does not add details for 'q' or 'limit'. The useful cost-on-failure note is behavioral rather than parameter-specific.

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 opens with a specific verb and resource: 'Disambiguate city names into Marketplace hubs — id + lat/lng.' This clearly distinguishes the tool from siblings like facebook_marketplace_search and facebook_marketplace_item, which handle listings rather than location resolution. It also names the key output fields, leaving no ambiguity about what the tool produces.

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 intended use case is implied by 'Disambiguate city names into Marketplace hubs' — an agent can infer it should be called when a city string needs resolving to a hub ID. However, it never explicitly states when to prefer this over the sibling search tools, nor does it mention any exclusions or preconditions. The guidance is present but left to inference.

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

All captapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources