PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Google ratings

pinmeto_get_google_ratings

Read-only

Get Google rating aggregates (average rating, total reviews, distribution) for all locations or a single store over a date range. Track reputation performance.

Instructions

Fetch Google rating statistics (averageRating, totalReviews, distribution) for all locations, or a single location.

Returns aggregate statistics only. For individual review text and sentiment analysis, use pinmeto_get_google_reviews.

Caching:

Results cached for 5 minutes (shared with reviews tool)
Use forceRefresh=true to bypass cache
Check structuredContent.cacheInfo for cache status

Data Lag Warning:

Google data has ~10 day lag. Requests with recent end dates may return incomplete data.
Check structuredContent.warning and warningCode for data completeness.

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)
`storeId`	No	Optional store ID to fetch a single location
`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	Ratings data: single location summary or array of location summaries (absent on error)
`error`	No	Error message if the request failed
`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
`warningCode`	No	Warning code for programmatic handling

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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"

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "averageRating": {
-        "description": "Average rating (1-5); 0 when the location has no reviews in range",
-        "maximum": 5,
-        "minimum": 0,
-        "type": "number"
-      },
-      "distribution": {
-        "additionalProperties": {
-          "minimum": 0,
-          "type": "number"
-        },
-        "description": "Rating distribution (e.g., {\"5\": 100, \"4\": 50})",
-        "type": "object"
-      },
-      "totalReviews": {
-        "description": "Total number of reviews",
-        "minimum": 0,
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "averageRating": {
-          "$ref": "#/properties/data/anyOf/0/properties/averageRating"
-        },
-        "distribution": {
-          "$ref": "#/properties/data/anyOf/0/properties/distribution"
-        },
-        "storeId": {
-          "description": "Store identifier",
-          "type": "string"
-        },
-        "totalReviews": {
-          "$ref": "#/properties/data/anyOf/0/properties/totalReviews"
-        }
-      },
-      "required": [
-        "storeId"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "averageRating": {
+        "description": "Average rating (1-5); 0 when the location has no reviews in range",
+        "maximum": 5,
+        "minimum": 0,
+        "type": "number"
+      },
+      "distribution": {
+        "additionalProperties": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "description": "Rating distribution (e.g., {\"5\": 100, \"4\": 50})",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "totalReviews": {
+        "description": "Total number of reviews",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "averageRating": {
+          "description": "Average rating (1-5); 0 when the location has no reviews in range",
+          "maximum": 5,
+          "minimum": 0,
+          "type": "number"
+        },
+        "distribution": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "number"
+          },
+          "description": "Rating distribution (e.g., {\"5\": 100, \"4\": 50})",
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "storeId": {
+          "description": "Store identifier",
+          "type": "string"
+        },
+        "totalReviews": {
+          "description": "Total number of reviews",
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "storeId"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

First observedv4.0.0Aug 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden of behavioral disclosure. It adds caching semantics (5-minute TTL, forceRefresh, cacheInfo), Google's ~10 day data lag with warning codes, and structured error handling (429, 404) with retryable flags. No contradiction with annotations.

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

Conciseness5/5

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

The description is organized into clear labeled sections: primary purpose, alternative tool, caching, data lag, and error handling. Every section serves a distinct purpose for invocation, and the most important info (what it returns and its scope) is front-loaded.

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?

Given the output schema exists and annotations cover read-only safety, the description covers all essential operational context: what it returns, how to get fresh data, how to check cache status, known data lag caveats, and how to handle errors programmatically. The agent has everything needed to invoke and interpret results correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by linking storeId to 'single location', explaining forceRefresh's purpose, and referencing structuredContent fields like cacheInfo and warningCode that clarify parameter-related behavior. This elevates it above baseline.

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 opens with 'Fetch Google rating statistics' naming a specific verb, resource, and the key data fields (averageRating, totalReviews, distribution). It also explicitly scopes to all locations or a single location, distinguishing it from sibling tools like pinmeto_get_google_reviews.

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?

Provides explicit routing guidance: 'For individual review text and sentiment analysis, use pinmeto_get_google_reviews.' Caching and data lag warnings further clarify when this tool is appropriate and when results may be incomplete, giving the agent actionable context for selection.

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

Deploy Server