PinMeTo Location MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINMETO_APP_ID | Yes | Your PinMeTo App ID | |
| PINMETO_ACCOUNT_ID | Yes | Your PinMeTo Account ID | |
| PINMETO_APP_SECRET | Yes | Your PinMeTo App Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pinmeto_get_locationA | Get details for a SINGLE location by store ID. Returns structured location data including address, contact info, and network connections. Error Handling:
|
| pinmeto_get_locationsA | Get ALL locations with pagination and filtering. Uses in-memory cache (5-min TTL) for fast queries on large datasets. Examples:
Error Handling:
|
| pinmeto_search_locationsA | Search ALL locations by name, address, store ID, or location descriptor. Returns lightweight results for quick discovery. Use pinmeto_get_location with storeId for full details. Error Handling:
|
| pinmeto_get_google_insightsA | Fetch Google metrics for all locations, or a single location if storeId provided. Supports time aggregation (default: total) and period comparisons. Comparison Options:
Data Lag Warning:
Error Handling:
|
| pinmeto_get_google_ratingsA | 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:
Data Lag Warning:
Error Handling:
|
| pinmeto_get_google_reviewsA | Fetch individual Google reviews with pagination and filtering for sentiment analysis. For aggregate statistics (averageRating, totalReviews), use pinmeto_get_google_ratings instead. Pagination:
Filtering:
Caching:
Data Lag Warning:
Error Handling:
|
| pinmeto_get_google_keywordsA | Fetch Google keywords for all locations, or a single location if storeId provided. Data Lag Warning:
Error Handling:
|
| pinmeto_get_google_review_insightsA | Summarize Google reviews into rating and sentiment statistics. Computes aggregates over the matched reviews server-side and returns the summary instead of the raw reviews, which is far more token-efficient than fetching them. The returned data is descriptive statistics, not LLM-written prose: read it and draw your own conclusions for the user. Analysis Types:
Large Dataset Handling:
Sampling Strategies (which reviews get analyzed):
Caching:
When NOT to use this tool:
|
| pinmeto_get_facebook_insightsA | Fetch Facebook metrics for all locations, or a single location if storeId provided. Supports time aggregation (default: total) and period comparisons. Comparison Options:
Error Handling:
|
| pinmeto_get_facebook_brandpage_insightsA | Fetch Facebook metrics for all brand pages. Supports time aggregation (default: total) and period comparisons. Comparison Options:
Error Handling:
|
| pinmeto_get_facebook_ratingsA | Fetch Facebook ratings for all locations, or a single location if storeId provided. Error Handling:
|
| pinmeto_get_apple_insightsA | Fetch Apple metrics for all locations, or a single location if storeId provided. Supports time aggregation (default: total) and period comparisons. Comparison Options:
Error Handling:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target clearly distinct resources and actions, with useful cross-references between ratings, reviews, and review insights. The only mild ambiguities are google_review_insights vs. google_ratings and facebook_insights vs. facebook_brandpage_insights, though descriptions do provide enough guidance to separate them.
Every tool follows the same pinmeto_get_<resource> pattern with snake_case naming. The lone action variation is search_locations, but it still fits the overall verb_noun convention and remains predictable.
Twelve tools is well-scoped for a location data and platform-insights server. Each tool covers a distinct data area, and there is no obvious redundancy or bloat despite the range of Google, Facebook, and Apple data.
The server provides solid read coverage for locations and platform analytics, but it is entirely read-only with no create, update, or delete operations for locations. Some platform coverage is also uneven, such as Facebook reviews missing despite Google reviews being available.