listingsapi-review-management
ListingsAPI review management
Turn the requested reviews into an actionable queue and reviewable reply drafts. Publishing or editing a reply is a public write and needs explicit approval of the text and targets.
Resolve the account and review scope
Use an existing MCP connection to 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 requires the API header. Never request a key in chat or include it in generated files. Reads need read access; replies need write access and the appropriate connected publisher profile. Day Pass excludes reviews.
Resolve locations using locations_search or locations_all. Set the date range, sources, ratings, and response status from the request; ask only for missing information needed to identify the right records. Read the runtime's tool schemas and relevant documentation before constructing arguments.
| Task | MCP tool | REST operation |
|---|---|---|
| Reviews for one location | reviews_list |
GET /locations/{locationId}/reviews |
| Account or tag queue | reviews_rollup |
GET /rollup_interactions |
| Re-read selected reviews | reviews_get |
GET /reviewDetails with interactionIds |
| Publish a new reply | reviews_respond |
POST /locations/reviews/respond |
| Edit an existing reply | reviews_edit_response |
POST /locations/reviews/respond/edit |
The rollup returns review records under data.rollupInteractions.edges[].node, with totalCount for the matching scope. It is not a per-store count report. tag defaults to all. Do not rely on locationFilters to constrain it: for a specific location set, use per-location reads or explicitly filter the fetched rollup to verified IDs. A clearly labeled partial subset can support useful drafts, but cannot establish a complete queue or per-store totals. These tools can also return questions and social mentions; distinguish them from reviews.