Skip to main content
Glama

run_leboncoin_locations_search

Resolve French place names or postcodes into leboncoin location objects with label, city, zipcode, department/region ID, and coordinates for targeted listing searches.

Instructions

Resolve a French place name or postcode into leboncoin location objects: label, city, zipcode, department/region id and coordinates. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_leboncoin_locations_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch term. e.g. Bordeaux
max_itemsNoMax items (up to 50)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the cost model ('1 point per returned record') and the shape of returned objects, which is genuinely useful. However, it says nothing about auth requirements, rate limits, or error behavior when a place name cannot be resolved.

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?

Two tightly written sentences with zero filler, front-loaded with the core action and followed by the return shape and cost. Every clause earns its place.

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?

With no output schema, the description correctly enumerates the returned fields, and it discloses the point cost. Given the low complexity (3 simple params, no nesting), this is nearly complete; only the absence of failure/precondition guidance keeps it from a 5.

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%, so the schema already documents all three parameters. The description adds modest value by clarifying that the keyword is specifically a place name or postcode, whereas the schema only says 'Search term. e.g. Bordeaux'. This is a small enhancement over the baseline.

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 a specific verb ('Resolve') and resource ('French place name or postcode into leboncoin location objects') and enumerates the returned fields. This clearly distinguishes it from sibling tools like run_leboncoin_listings or run_leboncoin_sellers, which retrieve different entities.

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?

Usage is implied by 'Resolve a French place name or postcode', but there is no explicit when-to-use guidance, no mention that this is typically a prerequisite for location-filtered listing searches, and no named alternatives. The agent must infer the workflow context.

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