Mencoro

Rank tracking by keyword cluster

get_cluster_breakdown

Read-onlyIdempotent

Rank-tracking metrics broken down per keyword cluster for a project over a date window: one row per cluster with its positions, share of voice and sentiment. Dates must fall within the data retention window. Answers questions like "which keyword clusters are strongest or weakest" or "how does my niche compare to my generic queries".

Input Schema

TableJSON Schema

Name	Required	Description
`dateTo`	Yes
`engines`	No	allowed values: chatgpt, claude, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping
`dateFrom`	Yes
`countries`	No	ISO-3166 alpha-2 country codes (e.g. "US", "GB", "DE"); a project's configured codes are listed by get_available_filters
`projectId`	Yes
`organizationId`	Yes
`queryClusterIds`	No	restrict to these keyword clusters
`includeUngroupedQueries`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes
`dataDirtySince`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / engines / description

Previous value: -"allowed values: chatgpt, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping"New value: +"allowed values: chatgpt, claude, perplexity, google_ai_overview, google_ai_mode, google_serp, google_shopping"

changedInput schema / properties / engines / items / enum

Previous value: -[
-  "chatgpt",
-  "perplexity",
-  "google_ai_overview",
-  "google_ai_mode",
-  "google_serp",
-  "google_shopping"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "google_ai_overview",
+  "google_ai_mode",
+  "google_serp",
+  "google_shopping"
+]

Changed2 schema fields changedSep 28, 2026

changedOutput schema / properties / rows / items / properties / mentionRate / description

Previous value: -"Percentage 0-100 of tracked queries with a result in the period; higher is better."New value: +"Percentage 0-100 of AI checks (one per tracked query x engine x UTC day) in the period that mentioned the brand, each check counted as the share of its passes that did; higher is better."

changedOutput schema / properties / rows / items / properties / serpRate / description

Previous value: -"Percentage 0-100 of tracked queries with a result in the period; higher is better."New value: +"Percentage 0-100 of traditional-search checks (one per tracked query x engine x UTC day) in the period in which the brand ranked; higher is better."

Changed26 schema fields changedSep 17, 2026
- addedOutput schema / properties / dataDirtySince / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / dataDirtySince / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / avgLinkPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / avgLinkPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / avgMentionCount / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / avgMentionCount / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / avgMentionPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / avgMentionPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / avgSerpPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / avgSerpPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / clusterId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / clusterId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / mentionRate / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / mentionRate / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / positivityIndex / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / positivityIndex / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / sentimentNegative / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / sentimentNegative / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / sentimentNeutral / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / sentimentNeutral / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / sentimentPositive / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / sentimentPositive / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / serpRate / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / serpRate / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / rows / items / properties / shareOfVoice / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / rows / items / properties / shareOfVoice / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
First observedSep 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the aggregation grain (one row per cluster) and an error-relevant constraint (dates must fall inside the data retention window), which an agent needs to avoid a failed call.

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 what the tool returns before describing use cases. The example questions add value rather than filler, though the sentence is a bit dense with enumerated fields.

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

Completeness3/5

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

An output schema exists, so return values need not be re-explained, and the tool's aggregation and date constraint are covered. However, half the parameters remain semantically undefined in both schema and description, which leaves gaps for an 8-parameter tool.

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

Parameters2/5

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

Schema description coverage is only 38% across 8 parameters. The description adds only the date-window/retention constraint; it says nothing about organizationId, projectId, dateFrom/dateTo formats, or includeUngroupedQueries, which are undocumented in the schema too. It does not compensate for the coverage gap.

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?

States a specific verb (rank-tracking metrics), resource (keyword clusters), scope (per project, date window), and the row shape (positions, share of voice, sentiment). This clearly distinguishes it from siblings like get_sentiment_breakdown, get_share_of_voice_formula, and list_clusters.

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?

Gives concrete usage context via example questions ('which clusters are strongest or weakest', 'niche vs generic queries') and a prerequisite (dates must fall within the retention window). It does not explicitly name which sibling to use instead when the agent wants per-query or time-series detail, so it falls short of full routing guidance.

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

All Mencoro 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.