Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook Marketplace item

facebook_marketplace_item_get
Read-onlyIdempotent

Fetches details for a Facebook Marketplace listing using its public URL or item ID, so you can inspect listing information without manual browsing.

Instructions

Get details for a Facebook Marketplace listing by item URL. Optional inputs: itemId and url.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_marketplace_item_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic Facebook Marketplace item URL.
itemIdNoFacebook Marketplace item identifier. Provide this instead of url when you already know the item id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds almost nothing beyond that — no note on login walls, missing/removed listings, rate limits, or which detail fields come back for a listing. The bar is lower with annotations present, but this still contributes little new behavioral context.

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?

Two short sentences with the resource and identifier front-loaded and no filler. It is efficient, though the second sentence largely repeats what the parameter names already convey.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, two of them infrastructure fields, and no output schema, the definition is only minimally complete: it never indicates what a listing detail payload contains (price, title, images, seller) or what happens when a listing is unavailable. An agent can call it correctly but cannot reason about the result.

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 that itemId should be used instead of url when the id is known. The description only restates that both are optional, and its 'Optional inputs' framing is slightly at odds with the schema's required context/llm_model fields. Baseline 3 applies since the schema carries the semantics.

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 names a specific verb and resource ('Get details for a Facebook Marketplace listing') and constrains it to a single item identified by URL, which clearly distinguishes it from list-style siblings such as facebook_marketplace_search_list. It stops short of naming a sibling, but the verb+resource is unambiguous.

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?

It implies this is the per-item lookup as opposed to a search/list call, but gives no explicit when-to-use or when-not-to-use guidance. The identification choice between itemId and url is deferred entirely to the schema, so the description adds only implied routing.

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

Deploy Server

Other Tools