Update to Listar

{
  "description": "How to use Listar to find the decision makers of a company and the professional phone and email of a person, one at a time or for a list.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: How to use Listar to find the decision makers of a company and the professional phone and email of a person, one at a time or for a list.\n---\n\n# Getting started with Listar\n\nListar finds B2B contact details: the decision makers of a company, and the professional email and phone of a named person. Coverage is complete for France and partial elsewhere.\n\n## Typical flow\n\n1. **Company first.** Call `find_company_contacts` with the company. The SIRET of the establishment or its official website domain identify it best; with a name only, add the city. It returns the company and its decision makers (name, job title, LinkedIn profile when known), without their phone or email.\n2. **Then the people you need.** Call `enrich_person` for each contact to reach: first name, last name, company, and the LinkedIn slug when `find_company_contacts` returned one. Ask for one channel only (`enrichmentType`) when the user needs only an email or only a phone.\n3. **Read `listarHints`.** When a company is not found, is registered in another city (often the holding of a group or franchise) or has no contacts, the hints say how to refine the search. Tell the user what was found instead of what was asked.\n\n## Lists\n\nFor several companies or people, launch every search with `wait: false`, then collect them all at once with `get_result` (`items`). Searches run in parallel and some take a few minutes.\n\n## Billing\n\nEvery result is billed to the Listar credit of the user's organization; a search that finds nothing is free. `get_credit_balance` shows the balance before a large batch. When the credit does not cover a search, the tool answers `insufficient_credit` and delivers nothing.\n\n## Wrong results\n\nWhen a delivered email bounces or a number belongs to someone else, report it with `report_result_issue` and the id that came with the result. Problems with the connector itself go to `send_feedback`.\n"
}