listingsapi-listing-audit
ListingsAPI listing audit
Produce an evidence-based health report for the requested locations. An audit does not authorize profile edits, connecting accounts, or duplicate suppression.
Establish scope and access
Use an already connected ListingsAPI MCP client at https://listingsapi.com/mcp, or the user's existing REST integration at https://listingsapi.com/api/v4. MCP supports its client OAuth flow or Authorization: API <key>; REST uses the API header. Keep credentials in the host's secret store or environment, never in chat or reports. Read access is sufficient for the audit. Do not install software, create credentials, or start a signup as part of it.
Resolve names or store codes with locations_search or locations_all. Record the returned location IDs and confirm ambiguous matches before continuing. For an account-wide request, page through all locations; otherwise stay within the requested set. A Day Pass can show demo-directory health only; label it as sandbox coverage.
Read available tool schemas before calling them. Use search_docs and get_doc for the relevant guide, or the linked REST docs below when using an existing API integration. MCP tools expose named fields; REST body wrappers are not automatically MCP arguments.