ListingsAPI performance reporting

Build a report with explicit dates, scope, denominators, and data coverage. Reporting does not authorize account connections, profile edits, replies, or post publication.

Scope the report

Use an existing MCP connection at https://listingsapi.com/mcp or the user's REST integration at https://listingsapi.com/api/v4. MCP accepts its OAuth flow or Authorization: API <key>; REST uses the API header. Read access is sufficient. Keep credentials out of prompts, reports, and logs. Day Pass excludes analytics and reviews.

Resolve the requested locations and comparison periods. State the date windows and relevant timezone; compare like-length complete periods unless the user requests otherwise. Resolve ambiguous location names and dates before calculating. Do not change scope just because some locations are easier to read.

Read runtime tool schemas before constructing requests. Use search_docs/get_doc or the endpoint docs to verify available metrics and date semantics.