PinMeTo Location MCP

Official

by PinMeTo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Facebook brand page insights

pinmeto_get_facebook_brandpage_insights

Read-only

Retrieve Facebook brand page metrics for any date range, with daily to yearly aggregation and period-over-period comparisons to track performance changes.

Instructions

Fetch Facebook metrics for all brand pages. 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 flat comparison fields (priorValue, delta, deltaPercent)

Error Handling:

Rate limit (429): errorCode="RATE_LIMITED", message includes retry timing
Auth failure (401): errorCode="AUTH_INVALID_CREDENTIALS"
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)
`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/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, and the description reinforces this while adding meaningful behavioral detail: comparison modes produce flat priorValue, delta, and deltaPercent fields, and errors expose structuredContent.errorCode and retryable with specific codes for rate limits and auth failures. This goes well beyond the annotation and helps an agent handle failures programmatically.

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 front-loaded with the core purpose and default behavior. The comparison and error sections use tight bullet-style formatting with no filler. Every sentence contributes operational information an agent needs.

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?

Combined with the rich input schema, output schema, and readOnlyHint annotation, the description covers the full call contract: required dates, aggregation choices, comparison behavior, response format, and error semantics. For a read-only metrics tool, nothing essential for invoking it correctly is missing.

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 schema already documents all parameters. The description adds value by explaining what compare_with modes mean (MoM/QoQ vs YoY), what comparison-active responses include, and that response_format=json is more token-efficient. It does not add date syntax, but the schema already provides patterns.

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

Purpose4/5

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

The description begins with a specific verb and resource: 'Fetch Facebook metrics for all brand pages.' It clearly identifies what the tool does and its scope. However, it does not explicitly distinguish itself from the sibling tool get_facebook_insights beyond the phrase 'brand page,' so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no direct guidance on when to use this tool versus alternatives. It does not mention sibling tools, exclusions, or conditions such as 'for location-level Facebook data use get_facebook_insights.' The scope is implied by 'all brand pages,' but an agent is not explicitly routed.

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

Deploy Server