Skip to main content
Glama
Sign In
fbmarket-mcp

fbmarket-mcp

by marchiani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Listing History

get_listing_history

Retrieve the complete price and observation history for a Facebook Marketplace listing to analyze trends, time-on-market, and potential sale triggers.

Instructions

Full timeline for one listing: every observation, every price change.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_listing_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesThe Facebook listing id (the digits in its marketplace URL).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.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. It does not disclose that this is a read-only operation, nor any limitations such as pagination or authentication requirements. The phrase 'every observation, every price change' hints at comprehensiveness but lacks explicit 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.

Conciseness5/5

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

The description is two concise clauses with zero waste, front-loading the core purpose. Every word contributes to defining the tool's function and scope.

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?

Despite having an output schema and a simple single-parameter tool, the lack of annotations means the description should explicitly state that this is a read-only operation and any constraints. It does not, leaving behavioral expectations unclear for an agent deciding whether to invoke it safely.

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?

The schema description coverage is 100%, fully documenting the listing_id parameter as the digits in the marketplace URL. The description adds no additional parameter information, meeting the baseline 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 states 'Full timeline for one listing' with a specific scope ('every observation, every price change'), which clearly identifies the verb (get) and resource (listing history). It distinguishes itself from siblings like get_daily_digest or get_watchlist by focusing on a single listing's timeline.

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 description implies usage for a single listing's history but does not explicitly state when to use it over alternatives or when not to. No sibling tools are referenced, so the agent must infer from the name and description that it is for a specific listing rather than a digest or watchlist.

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