Skip to main content
Glama
Sign In
fbmarket-mcp

fbmarket-mcp

by marchiani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Searches

list_searches

Displays saved searches and their listing counts, letting you compare which search criteria produce the most Facebook Marketplace results.

Instructions

The saved searches in config.toml and how many listings each has produced.

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": "list_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full responsibility for behavioral transparency. It indicates a read-only operation (reading config.toml and producing counts), but does not explicitly mention that no modifications occur or that there are no side effects. It also does not clarify whether it might access external listing data or just the config file.

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 concise sentence with no redundancy or filler. It conveys the essential information about what the tool does without unnecessary detail.

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 no-parameter tool, the description provides sufficient context: it lists saved searches and their listing counts. The output schema is not provided, but the description gives a general idea of the output structure. It could be slightly more explicit about the format or types of data returned, but it is adequate for basic usage.

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

Parameters5/5

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

The tool has no parameters, as shown in the input schema. The description does not need to explain parameter semantics because there are none, and the schema coverage is 100% with zero properties. This is perfectly adequate.

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 clearly states the tool returns saved searches from config.toml and their listing counts. It implies a 'list' operation, and the name 'list_searches' is self-explanatory. However, it lacks explicit distinction from sibling tools like 'get_watchlist' or 'get_daily_digest', though the function is reasonably clear.

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 does not explicitly state when to use this tool versus alternatives such as 'search_listings' or 'run_daily_scan'. It provides no usage context or prerequisites, leaving the agent to infer based on the name and description alone.

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