PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Facebook ratings

pinmeto_get_facebook_ratings

Read-only

Retrieve Facebook ratings for all locations or a specific store by ID within a date range. Provides JSON or markdown output for easy analysis.

Instructions

Fetch Facebook ratings for all locations, or a single location if storeId provided.

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
`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.4/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint annotation by detailing specific error behavior: rate limit (429), not found (404), and programmatic handling via structuredContent.errorCode and .retryable. This gives an agent actionable expectations for unexpected responses.

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 main behavior is stated in one frontloaded sentence, with error handling kept in tight bullet points. No redundant text or repetition of schema definitions.

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

Completeness4/5

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

The description covers the core call semantics, optional filtering, and error handling. The output_schema covers return values, and the schema covers parameters, so nothing critical is missing. Minor gap: no mention of pagination or date-range constraints, but these are not essential for a correct call.

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 the baseline is 3. The description adds meaningful clarification for storeId ('all locations, or a single location if storeId provided'), which is not fully expressed in the schema alone. It does not need to repeat date/format details already in the schema.

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?

Uses a specific verb ('Fetch') plus a clear resource ('Facebook ratings') and explicitly describes the two scopes: all locations or a single location when storeId is provided. This clearly distinguishes it from sibling tools like facebook_insights and google_ratings.

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

Usage Guidelines3/5

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

The description gives a clear usage context: use it for Facebook ratings, with an optional storeId filter. However, it does not explicitly state when to prefer this tool over alternatives (e.g., insights or review tools) or when not to use it.

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

Deploy Server