Mencoro

Organization brand overview

get_organization_overview

Read-onlyIdempotent

Latest-snapshot rank-health board across the active projects the caller can access in an organization: one row per brand (share of voice, mention rate, average mention position, positivity, tracked-query count in total and per engine family: AI, SERP, Shopping) 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".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>"
    },
    "name": "get_organization_overview"
  }
}

Input Schema

Name	Required	Description	Default
`organizationId`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedOutput schema / properties / projects / items / properties / aiTrackedQueryCount

Added value: +{
+  "description": "How many of trackedQueryCount run on an AI answer engine (ChatGPT, Claude, Perplexity, Google AI Overview, Google AI Mode).",
+  "type": "integer"
+}

addedOutput schema / properties / projects / items / properties / serpTrackedQueryCount

Added value: +{
+  "description": "How many of trackedQueryCount run on classic Google SERP.",
+  "type": "integer"
+}

addedOutput schema / properties / projects / items / properties / shoppingTrackedQueryCount

Added value: +{
+  "description": "How many of trackedQueryCount run on Google Shopping.",
+  "type": "integer"
+}

addedOutput schema / properties / projects / items / properties / trackedQueryCount / description
```
Added value: +"Configured tracked queries of the project, paused ones included."
```

changedOutput schema / properties / projects / items / required

Previous value: -[
-  "projectId",
-  "name",
-  "status",
-  "trackedQueryCount"
-]New value: +[
+  "projectId",
+  "name",
+  "status",
+  "trackedQueryCount",
+  "aiTrackedQueryCount",
+  "serpTrackedQueryCount",
+  "shoppingTrackedQueryCount"
+]

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.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the key behavioral trait that annotations cannot: this is a snapshot with NO date window, results are sorted by share of voice, only active projects the caller can access are included, and an organization-level aggregate row is appended. That is exactly the non-obvious context an agent needs.

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 purpose and snapshot semantics, then exclusions, then an example question. The first sentence is a long run-on with a nested parenthetical field list, which slightly hurts scanability, but every clause carries information.

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?

An output schema exists, so return values need no further explanation; the description nonetheless summarizes row shape and ordering. With strong annotations and a single required param, nothing material is missing for correct invocation.

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 0% and the single parameter (organizationId) is undocumented, but the description implies its role by saying the board covers 'the active projects the caller can access in an organization.' It does not say where the id comes from or its format, which is a real but modest gap for a one-parameter tool.

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?

Names a specific verb+resource (rank-health board / brand overview) and enumerates exactly what each row contains (share of voice, mention rate, average mention position, positivity, tracked-query counts per engine family) plus the org-level aggregate. It also distinguishes itself from the sibling get_project_rank_tracking_stats by scope (organization-wide vs per-project).

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?

Explicitly states when to use it (current-state company-wide summary) and when not to (any date-ranged comparison), and routes the agent to the correct alternative: "call the per-project tools (e.g. get_project_rank_tracking_stats) for each project id returned here." That also clarifies the call pattern for the alternative.

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.