PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Google insights

pinmeto_get_google_insights

Read-only

Fetch Google search metrics for all locations or a specific store, with time aggregation and period comparisons to track performance changes. Handles data lag and errors via structured codes.

Instructions

Fetch Google metrics for all locations, or a single location if storeId provided. Supports time aggregation (default: total) and period comparisons.

Comparison Options:

compare_with="prior_period": Compare with same-duration period before (MoM, QoQ)
compare_with="prior_year": Compare with same dates last year (YoY)
When comparison is active, each metric includes a comparison field with prior, delta, deltaPercent

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
`aggregation`	No	Time aggregation: total (default, maximum token reduction), daily, weekly, monthly, quarterly, half-yearly, yearly	total
`compare_with`	No	Compare with: prior_period (MoM/QoQ for same-duration period before), prior_year (YoY for same dates last year), or none (default)	none
`response_format`	No	Response format: "json" (default, token-efficient) or "markdown" (human-readable with tables)	json

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Error message if the request failed
`warning`	No	Warning message (e.g., incomplete data due to lag)
`insights`	No	Array of insights by metric. Flattened (no values array) when aggregation=total, multi-period otherwise (absent on error)
`errorCode`	No	Error code for programmatic handling
`retryable`	No	Whether the operation can be retried
`compareWith`	No	Comparison period type used: "none", "prior_period", or "prior_year"
`periodRange`	No	Date range for the current period data
`warningCode`	No	Warning code for programmatic handling
`comparisonError`	No	Error message if comparison data could not be fetched (current period data still returned)
`timeAggregation`	No	Time aggregation level applied to the data (e.g., "total", "monthly", "daily")
`priorPeriodRange`	No	Date range for the prior period (present when compare_with is specified)

Schema Changelog

Changes observed during successful MCP inspections.

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

removedOutput schema / properties / priorPeriodRange / $ref
```
Removed value: -"#/properties/periodRange"
```
addedOutput schema / properties / priorPeriodRange / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / priorPeriodRange / properties

Added value: +{
+  "from": {
+    "description": "Start date (YYYY-MM-DD)",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  },
+  "to": {
+    "description": "End date (YYYY-MM-DD)",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  }
+}

addedOutput schema / properties / priorPeriodRange / required
```
Added value: +[
+  "from",
+  "to"
+]
```
addedOutput schema / properties / priorPeriodRange / type
```
Added value: +"object"
```

First observedv4.0.0Aug 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing the ~10 day Google data lag, incomplete-data warnings, rate-limit error codes, not-found behavior, and retryable flags. This gives the agent actionable expectations about latency and error handling.

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 one-line purpose is followed by well-labeled sections for comparison options, data lag, and error handling. Every block serves a distinct operational need, and the structure makes the information easy to consume.

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 the description covers core behavior, data-lag caveats, and error handling, an agent has what it needs to invoke this tool correctly. The description is complete for a read-only metrics tool with six well-documented parameters.

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?

Input schema covers 100% of parameters, so the baseline is already strong. The description adds extra meaning beyond the schema by explaining what the comparison output looks like (prior, delta, deltaPercent) and by detailing storeId's single-location behavior. This is helpful but mostly reinforces and slightly extends schema content.

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 a specific verb and resource: 'Fetch Google metrics for all locations, or a single location if storeId provided.' This clearly distinguishes the tool from siblings focused on ratings, reviews, keywords, or Facebook/Apple data. It also states the key scope and filtering behavior.

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

Usage Guidelines4/5

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

The description clearly explains when to use it: for Google metrics, with optional single-location filtering via storeId, and with optional comparison/aggregation settings. It does not explicitly name alternatives or tell the agent when not to use this tool, but the context is clear enough for selection among siblings.

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

Deploy Server