Skip to main content
Glama
Sign In
fbmarket-mcp

fbmarket-mcp

by marchiani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Collection Status

get_collection_status

Check collection progress to determine whether Facebook Marketplace analytics are ready for reliable use.

Instructions

How much data has been collected, and how far to trust the analytics yet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations and no description of side effects, read-only nature, or data access, the tool's behavior is completely opaque. The description does not disclose whether it is safe, mutating, or resource-intensive.

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

Conciseness2/5

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

The description is very short but cryptic and poorly structured. It reads like a sentence fragment rather than a clear, concise explanation, and the wording 'how far to trust the analytics yet' is ambiguous and not easily parsed.

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

Completeness1/5

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

The description provides no information about the output schema, return values, or how the status relates to the overall workflow. An agent cannot infer what to expect from calling this tool.

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 tool has no parameters, so schema coverage is trivially complete. The description adds no parameter information, but none is needed; the baseline of 3 applies.

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 is phrased as a vague question rather than a clear statement of functionality. It mentions data collection and analytics trust but does not explicitly say what the tool does or returns, making it difficult for an agent to understand the tool's purpose.

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?

There is no guidance on when to use this tool versus the sibling tools. No context, conditions, or alternative suggestions are provided, leaving the agent without direction on selection.

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