Mencoro

Organization brand overview

get_organization_overview

Read-onlyIdempotent

Latest-snapshot rank-health board across all active projects in an organization: one row per brand (share of voice, mention rate, average mention position, positivity, tracked-query count) ranked by share of voice, plus an organization-level aggregate. This is a current-state snapshot and takes NO date window; for date-ranged comparison, call the per-project tools (e.g. get_project_rank_tracking_stats) for each project id returned here. Answers questions like "give me a company-wide summary of share of voice and sentiment across all my projects".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`organizationId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`projects`	Yes
`aggregate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / properties / projects / 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) across all retained data that mentioned the brand, each check counted as the share of its passes that did; higher is better."

Changed16 schema fields changedSep 17, 2026
- addedOutput schema / properties / aggregate / properties / avgMentionPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / aggregate / properties / avgMentionPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / aggregate / properties / avgMentionRate / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / aggregate / properties / avgMentionRate / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / aggregate / properties / avgPositivityIndex / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / aggregate / properties / avgPositivityIndex / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / aggregate / properties / avgShareOfVoice / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / aggregate / properties / avgShareOfVoice / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / projects / items / properties / avgMentionPosition / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / projects / items / properties / avgMentionPosition / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / projects / items / properties / mentionRate / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / projects / items / properties / mentionRate / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / projects / items / properties / positivityIndex / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / projects / items / properties / positivityIndex / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```
- addedOutput schema / properties / projects / items / properties / shareOfVoice / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / projects / items / properties / shareOfVoice / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds the key behavioral constraint that it takes NO date window and is a current-state snapshot, plus it discloses the return shape (one row per brand + org aggregate). It does not mention pagination or result limits, but with annotations and an output schema present, this is a meaningful add.

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?

Front-loaded with the resource and metric list, then scoping constraint, then the alternative-routing sentence. Dense but every sentence earns its place; slightly long metric enumeration keeps it from a 5.

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 an output schema exists (so return shape need not be re-explained) and a single obvious required param, the description covers purpose, scope, metric semantics, and alternative routing. An agent has everything needed to select and invoke it correctly.

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?

Only one parameter (organizationId) at 0% schema description coverage, so the schema says nothing about it. The description does not explain what organizationId accepts (format, source), but for a single obvious required id the gap is minor. Baseline 3 for a low-coverage single-param tool where the description adds no syntax.

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 names a specific resource (organization-wide brand rank-health board), enumerates the exact metrics returned (share of voice, mention rate, average mention position, positivity, tracked-query count), and states the row granularity (one row per brand). It distinguishes itself from siblings by naming get_project_rank_tracking_stats as the date-ranged alternative.

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

Usage Guidelines5/5

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

Explicit when-to-use (company-wide snapshot, no date window) and when-not (date-ranged comparison), naming the alternative tool and the workflow (call per-project tools for each project id returned here). It even provides a routing example question.

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.