Skip to main content
Glama
Sign In

Rawa

by ai.rawa.mcp
OverviewDiscussionsAdmin

Get brand analysis

get_brand_analysis
Read-onlyIdempotent

Use this when the user wants the story rather than the numbers: the latest written analysis Rawa made of the brand's marketing performance, one per connected account (pass account for one).

Input Schema

NameRequiredDescriptionDefault
accountNoOne connected account to read. Omit it for every connected analytics account; each comes back on its own, never combined.
brandIdNoA brand id from get_workspace or list_brands, or the brand's name. Omit it when the organization has a single brand.

Output Schema

NameRequiredDescriptionDefault
accountsYesThe newest analysis of each connected analytics account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / account
      Added value: +{
+  "additionalProperties": false,
+  "description": "One connected account to read. Omit it for every connected analytics account; each comes back on its own, never combined.",
+  "properties": {
+    "accountId": {
+      "description": "The account's id, as a result's account.accountId names it.",
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "platform": {
+      "description": "The account's platform, as a result's account.platform names it.",
+      "enum": [
+        "instagram",
+        "facebook",
+        "tiktok",
+        "meta_ads",
+        "linkedin",
+        "linkedin_ads",
+        "tiktok_ads",
+        "google_ads",
+        "snapchat_ads",
+        "shopify"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "platform",
+    "accountId"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / accounts
      Added value: +{
+  "description": "The newest analysis of each connected analytics account.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account": {
+        "additionalProperties": false,
+        "description": "The connected account every number beside it belongs to.",
+        "properties": {
+          "accountId": {
+            "type": "string"
+          },
+          "accountName": {
+            "type": "string"
+          },
+          "platform": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "platform",
+          "accountId",
+          "accountName"
+        ],
+        "type": "object"
+      },
+      "analysisType": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "hasAnalysis": {
+        "type": "boolean"
+      },
+      "headline": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "insights": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "evidence": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "metric": {
+                    "type": "string"
+                  },
+                  "note": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "source": {
+                    "type": "string"
+                  },
+                  "value": {
+                    "type": "number"
+                  },
+                  "windowDays": {
+                    "type": [
+                      "number",
+                      "null"
+                    ]
+                  }
+                },
+                "required": [
+                  "source",
+                  "metric",
+                  "value",
+                  "windowDays",
+                  "note"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "kind": {
+              "enum": [
+                "metric_fact",
+                "actionable"
+              ],
+              "type": "string"
+            },
+            "narrative": {
+              "type": "string"
+            },
+            "recommendation": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "kind",
+            "title",
+            "narrative",
+            "evidence",
+            "recommendation"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "omittedInsights": {
+        "type": "number"
+      },
+      "summary": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "account",
+      "hasAnalysis"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / analysisType
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / createdAt
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / hasAnalysis
      Removed value: -{
-  "type": "boolean"
-}
    • removedOutput schema / properties / headline
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / insights
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "evidence": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "metric": {
-              "type": "string"
-            },
-            "note": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "source": {
-              "type": "string"
-            },
-            "value": {
-              "type": "number"
-            },
-            "windowDays": {
-              "type": [
-                "number",
-                "null"
-              ]
-            }
-          },
-          "required": [
-            "source",
-            "metric",
-            "value",
-            "windowDays",
-            "note"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "kind": {
-        "enum": [
-          "metric_fact",
-          "actionable"
-        ],
-        "type": "string"
-      },
-      "narrative": {
-        "type": "string"
-      },
-      "recommendation": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "title": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "title",
-      "narrative",
-      "evidence",
-      "recommendation"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / omittedInsights
      Removed value: -{
-  "type": "number"
-}
    • removedOutput schema / properties / summary
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedOutput schema / required
      Previous value: -[
-  "hasAnalysis"
-]New value: +[
+  "accounts"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / brandId / description
      Previous value: -"A brand id from get_workspace or list_brands. Omit it when the organization has a single brand."New value: +"A brand id from get_workspace or list_brands, or the brand's name. Omit it when the organization has a single brand."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: results are the *latest* analysis and come back 'one per connected account... never combined', which tells the agent to expect a fan-out rather than a merged document. It doesn't mention what a missing analysis yields or how fresh the analysis is.

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?

A single sentence, front-loaded with the usage cue and followed by the resource description and the per-account scoping note. No filler or redundant phrasing.

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?

An output schema exists, so return-value shape needn't be explained, and the multi-account fan-out plus optional account filter is covered. The remaining gap is edge-case behavior — what is returned when no analysis has been produced yet, or whether results are ordered/paginated.

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 coverage is 100% and the nested account object already documents platform/accountId and the omit-for-all behavior, so the schema does the heavy lifting. The description restates the single-account case ('pass account for one') and says nothing about brandId, adding little meaning beyond structured fields. Baseline 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?

The description names a specific resource — 'the latest written analysis Rawa made of the brand's marketing performance' — and frames it as 'the story rather than the numbers', which implicitly separates it from a metrics tool like get_performance_overview. It is clear what is returned, though it never names a sibling tool outright.

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?

'Use this when the user wants the story rather than the numbers' gives an explicit selection condition tied to narrative-vs-metric intent, which is genuinely actionable. It stops short of a full when-not statement (e.g., when to prefer the numeric overview, or what to do when no analysis exists).

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

All Rawa toolsInspect
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.

Resources