Facebook Scraper3 MCP Server

listing_details

Extract detailed information from Facebook Marketplace listings to analyze products, prices, and seller data for research or comparison purposes.

Instructions

Get listing details

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listing_details"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get listing details' implies a read-only operation, but it does not specify permissions, rate limits, error conditions, or the format of returned details. This is inadequate for a tool with no annotation coverage, as critical behavioral traits are omitted.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It is front-loaded and appropriately sized for a tool with no parameters, making it highly concise and well-structured.

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 the tool's complexity (implied by sibling tools suggesting data retrieval) and lack of annotations and output schema, the description is incomplete. It does not explain what a 'listing' is, what details are returned, or how it differs from similar tools, leaving significant gaps for an agent to understand its full context and use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter information, which is acceptable given the schema's completeness. A baseline of 4 is appropriate as the description does not compensate for any gaps, but none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get listing details' restates the tool name 'listing_details' with minimal elaboration, making it tautological. It specifies a verb ('Get') and resource ('listing details') but lacks specificity about what a 'listing' refers to in this context or what details are retrieved, failing to distinguish it from sibling tools like 'page_details' or 'profile_details_by_url'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'page_details', 'profile_details_by_url', and 'search', the description offers no context, prerequisites, or exclusions, leaving the agent without direction on appropriate usage scenarios.

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