PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Google reviews

pinmeto_get_google_reviews

Read-only

Fetch individual Google reviews with pagination and filtering by date, rating, and response status. Analyze customer sentiment and find unresponded reviews for follow-up.

Instructions

Fetch individual Google reviews with pagination and filtering for sentiment analysis.

For aggregate statistics (averageRating, totalReviews), use pinmeto_get_google_ratings instead.

Pagination:

limit: Max reviews to return (default: 50, max: 500)
offset: Skip first N reviews (for pagination)
Check hasMore in response to know if more pages exist

Filtering:

minRating/maxRating: Filter by rating range (1-5)
hasResponse: true for responded reviews, false for unresponded

Caching:

Results cached for 5 minutes (shared with ratings tool)
Use forceRefresh=true to bypass cache
Filters are applied client-side on cached data

Data Lag Warning:

Google data has ~10 day lag. Requests with recent end dates may return incomplete data.

Error Handling:

Rate limit (429): errorCode="RATE_LIMITED", message includes retry timing
Not found (404): errorCode="NOT_FOUND" if storeId doesn't exist
All errors: check structuredContent.errorCode and .retryable for programmatic handling

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	End date (YYYY-MM-DD)
`from`	Yes	Start date (YYYY-MM-DD)
`limit`	No	Max reviews to return (default: 50, max: 500)
`offset`	No	Skip first N reviews for pagination
`storeId`	No	Optional store ID to fetch a single location
`maxRating`	No	Maximum rating filter (1-5)
`minRating`	No	Minimum rating filter (1-5)
`hasResponse`	No	Filter: true for responded reviews, false for unresponded
`forceRefresh`	No	Bypass cache and fetch fresh data
`response_format`	No	Response format: "json" (default, token-efficient) or "markdown" (human-readable with tables)	json

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Array of reviews (absent on error)
`error`	No	Error message if the request failed
`limit`	No	Requested limit
`offset`	No	Current offset position
`hasMore`	No	Whether more results exist beyond offset+limit
`warning`	No	Warning message (e.g., incomplete data due to lag)
`cacheInfo`	No	Cache status information
`errorCode`	No	Error code for programmatic handling
`retryable`	No	Whether the operation can be retried
`totalCount`	No	Total reviews matching filters
`warningCode`	No	Warning code for programmatic handling

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv4.3.0Sep 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / to / $ref
```
Removed value: -"#/properties/from"
```
addedInput schema / properties / to / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
addedInput schema / properties / to / type
```
Added value: +"string"
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv4.0.0Aug 10, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: 5-minute caching, client-side filter application, forceRefresh bypass, a ~10 day Google data lag, and structured error codes (RATE_LIMITED, NOT_FOUND) with retryability. This is substantial value beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with clear section headings. Each section serves a purpose: purpose distinction, pagination, filtering, caching, data lag, and error handling. Some redundancy exists with schema parameter descriptions, but the organization makes it easy for an agent to scan and extract key semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all operational aspects an agent needs: pagination with hasMore, filtering, caching with refresh, data lag caveats, error handling format, and a clear sibling alternative. With an output schema present, no explanation of return fields is needed. The description is complete for correct invocation and result interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover all 10 parameters (100% coverage). The description enhances this by explaining pagination semantics (hasMore), the client-side filtering behavior on cached data, and forceRefresh's effect, which goes beyond the schema. Not a 5 because much of the parameter info is redundant with the schema, but it does add meaningful usage context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Fetch individual Google reviews') with a clear resource and purpose ('for sentiment analysis'). It explicitly differentiates from the sibling pinmeto_get_google_ratings by contrasting individual reviews with aggregate statistics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to use this tool vs. an alternative: 'For aggregate statistics (averageRating, totalReviews), use pinmeto_get_google_ratings instead.' It also provides concrete pagination/filtering usage in separate sections, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server