Evendo Place Score
Beyond review averages
Evendo Place Score is Evendo's proprietary assessment of each place's popularity and quality. It is designed to provide a stronger discovery and ranking signal than relying only on average customer ratings. A score is not the same as a 0–5 review rating, nor a guarantee of an individual visitor's experience.
| Property | Contract |
|---|---|
| Field | place_score |
| Scale | 0 to 100 (numeric) |
| Direction | Higher is better |
| Scope | Intended for all venue types |
| Typical values | Most venues score 20–50; 70+ is excellent; 90+ is a city's very best |
| MCP minimum filter | min_place_score |
| MCP ordering | sort_by: "place_score" |
| GraphQL range filters | place_score_gte, place_score_lte |
| GraphQL sort field | PLACE_SCORE |
MCP example
Use with find_venues after resolving the destination ID:
json
{
"place_id": "27799",
"venue_type": "Attractions",
"min_place_score": 80,
"sort_by": "place_score",
"limit": 10
}GraphQL example
graphql
query {
descendantsOf(
ancestorId: "27799"
nodeType: "Attractions"
place_score_gte: 80
orderBy: { field: PLACE_SCORE, direction: DESC }
first: 10
) {
edges { node { id title place_score rating rating_votes } }
pageInfo { hasNextPage endCursor }
}
}These arguments are live in MCP and GraphQL. Some sample outputs elsewhere in these docs were captured before Place Score was added, so they do not show it.
Interpretation and recommendations
- Use score thresholds when a user asks for the best or highest-quality options.
- Combine Place Score with geographic and user-preference constraints, including accessibility, category and price.
- Use customer ratings and review counts as supplementary context, not substitutes for Place Score.
- A missing score means unknown, not zero. Do not fabricate scores or silently treat missing as a poor ranking.
- Do not present the metric as a percentage probability, external certification or independently verified review score. The scoring formula and update schedule are not publicly specified.