Maqui Analytics

Reseñas

get_reviews

Read-only

[DEMO SINTÉTICA] Reseñas de Google Business Profile y otras plataformas (Facebook): rating promedio, conteo total, tasa de respuesta y últimas reseñas con autor, rating, texto y si fueron respondidas. Sirve para "reseñas", "reputación", "qué dicen los clientes", "rating en Google", "reviews".

Input Schema

Name	Required	Description	Default
`date_range`	No	Período a consultar. Ejemplos: "últimos 30 días", "enero 2025", "2025-01-01 a 2025-01-31", "este mes", "mes pasado". Por defecto: últimos 30 días.
`min_rating`	No	Filtrar reseñas con rating mínimo (1-5). Omitir para ver todas.

Output Schema

Name	Required	Description
`data`	Yes	Reputación y reseñas del período.
`demo`	No	Solo aparece en demo; todos sus datos son ficticios.
`notice`	No	Aviso obligatorio de datos sintéticos cuando demo es true.
`sample_period`	No	Período fijo de los ejemplos sintéticos; no cambia al solicitar otro rango.
`requested_period`	No	Rango solicitado a la demo; no es el período real de sus ejemplos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "Estadísticas de la cuenta autenticada en data. Si demo es true, son ejemplos sintéticos; sample_period es su período y requested_period solo el rango solicitado.",
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "description": "Reputación y reseñas del período.",
+      "properties": {
+        "avgRating": {
+          "description": "Rating promedio en escala 1 a 5; excluye Facebook. null si no hay ratings numéricos.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "period": {
+          "additionalProperties": false,
+          "description": "Rango consultado, desde from hasta to inclusive.",
+          "properties": {
+            "from": {
+              "description": "Fecha YYYY-MM-DD.",
+              "format": "date",
+              "type": "string"
+            },
+            "to": {
+              "description": "Fecha YYYY-MM-DD.",
+              "format": "date",
+              "type": "string"
+            }
+          },
+          "required": [
+            "from",
+            "to"
+          ],
+          "type": "object"
+        },
+        "responseRate": {
+          "description": "Reseñas con respuesta del propietario / total; 0 si no hay reseñas. Porcentaje: 5 significa 5%, no 0,05.",
+          "type": "number"
+        },
+        "reviews": {
+          "description": "Hasta 20 reseñas, de más reciente a más antigua; total puede ser mayor.",
+          "items": {
+            "additionalProperties": false,
+            "description": "Reseña individual.",
+            "properties": {
+              "author_name": {
+                "description": "Nombre del autor.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "has_reply": {
+                "description": "1 si el propietario respondió; 0 si no.",
+                "enum": [
+                  0,
+                  1
+                ],
+                "type": "number"
+              },
+              "platform": {
+                "description": "Plataforma de origen.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "rating": {
+                "description": "Rating en escala 1 a 5; null para reseñas sin rating.",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "review_date": {
+                "description": "Fecha de reseña según la fuente.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "review_text": {
+                "description": "Texto de la reseña; null si no existe.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "author_name",
+              "rating",
+              "review_text",
+              "review_date",
+              "platform",
+              "has_reply"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total": {
+          "description": "Reseñas del período que pasan el filtro, incluidas las de Facebook sin rating.",
+          "type": "number"
+        }
+      },
+      "required": [
+        "period",
+        "total",
+        "avgRating",
+        "responseRate",
+        "reviews"
+      ],
+      "type": "object"
+    },
+    "demo": {
+      "const": true,
+      "description": "Solo aparece en demo; todos sus datos son ficticios.",
+      "type": "boolean"
+    },
+    "notice": {
+      "description": "Aviso obligatorio de datos sintéticos cuando demo es true.",
+      "type": "string"
+    },
+    "requested_period": {
+      "additionalProperties": false,
+      "description": "Rango solicitado a la demo; no es el período real de sus ejemplos.",
+      "properties": {
+        "from": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        },
+        "to": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        }
+      },
+      "required": [
+        "from",
+        "to"
+      ],
+      "type": "object"
+    },
+    "sample_period": {
+      "additionalProperties": false,
+      "description": "Período fijo de los ejemplos sintéticos; no cambia al solicitar otro rango.",
+      "properties": {
+        "from": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        },
+        "to": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        }
+      },
+      "required": [
+        "from",
+        "to"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedMay 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds one real behavioral fact beyond them — that data spans Google Business Profile AND Facebook — but says nothing about refresh cadence, account/location scoping, or why Google is named first while the title implies only reviews.

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

Conciseness4/5

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

Two sentences, front-loaded with the substantive payload before the intent keywords. The keyword string is somewhat stuffed and the '[DEMO SINTÉTICA]' prefix is noise, but neither obscures the core statement.

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?

With an output schema present, the description needn't document return structure, and the 100%-covered two-param schema needs no explanation. What it covers — sources, metrics, and routing intents — is sufficient to call the tool correctly; only the multi-location/multi-account scoping question is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters (date_range with worked format examples and a default, min_rating with its 1-5 range) are fully documented in the schema. The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: retrieves Google Business Profile and Facebook reviews, and enumerates the payload (average rating, total count, response rate, latest reviews with author/rating/text/response status). This is far more specific than a title restatement, and no sibling tool covers reviews, though it never explicitly names a sibling it differs from.

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 'sirve para' clause maps concrete user intents ("reseñas", "reputación", "qué dicen los clientes", "rating en Google") onto this tool, which is genuinely useful routing guidance for an agent choosing among 21 summary/list tools. It stops short of stating when NOT to use it or which sibling to pick when the user wants ads or traffic data instead.

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

All Maqui Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.