Rawa

List recent posts

list_recent_posts

Read-onlyIdempotent

Posts synced from the brand's connected channels, whoever published them, with their metrics: newest first, each with its caption, link, and its latest daily reach, views, likes, comments, shares, saves, follows and engagement rate as of metrics.day (a metric the channel does not report is left out), plus the sentiment and recurring themes of its comments where Rawa has analysed them. For what Rawa itself has scheduled or sent, use list_publications.

Input Schema

Name	Required	Description
`limit`	No	How many to return. Defaults to 20.
`brandId`	No	A brand id from get_workspace or list_brands, or the brand's name. Omit it when the organization has a single brand.
`platform`	No	Only this channel. Omit for all of them.
`lookbackDays`	No	How many days back to look. Defaults to 30.

Output Schema

Name	Required	Description	Default
`posts`	Yes
`truncated`	Yes
`lookbackDays`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 3, 2026
- addedOutput schema / properties / posts / items / properties / metrics / properties / day
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / posts / items / properties / metrics / properties / fetchedAt
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / posts / items / properties / metrics / properties / follows
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / posts / items / properties / metrics / properties / impressions
```
Removed value: -{
-  "type": "number"
-}
```
- changedOutput schema / properties / posts / items / properties / metrics / required
```
Previous value: -[
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "fetchedAt"
-]New value: +[
+  "day"
+]
```

Changed1 schema field changedNov 3, 2026

changedOutput schema / properties / posts / items / properties / metrics / required

Previous value: -[
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "reach",
-  "fetchedAt"
-]New value: +[
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "fetchedAt"
+]

Changed1 schema field changedOct 29, 2026

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."

First observedOct 23, 2026

TDQS

A4.1/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 safety is covered. The description adds real behavioral detail beyond them: newest-first ordering, that an unreported metric is simply omitted, and that sentiment/themes only appear where Rawa has analysed comments. These conditional-presence rules are the kind of context an agent cannot get from the annotations.

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

Conciseness3/5

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

Purpose and the sibling alternative bracket the description well, and it is front-loaded. However, the long enumeration of return metrics (reach, views, likes, comments, shares, saves, follows, engagement rate) largely duplicates what the existing output schema already declares, weakening the 'every sentence earns its place' test.

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?

With a rich output schema, full annotation coverage and 100% schema description coverage, the description only needs scope, ordering and sibling routing — all of which it supplies. Nothing an agent needs to call this correctly is missing.

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 every parameter (limit, brandId, platform, lookbackDays) is documented in the schema with defaults and enum values. The description adds only indirect hints — 'whoever published them' signals there is no author filter, and 'newest first' signals ordering is not parameterized — so the schema does the heavy lifting and baseline 3 applies.

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+resource (posts synced from the brand's connected channels) with an explicit scope qualifier ('whoever published them') and ordering ('newest first'). It also names the sibling it is not (list_publications), so an agent can distinguish the two without opening either schema.

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 an explicit routing rule: for content Rawa itself scheduled or sent, use list_publications instead. That resolves the main ambiguity with the closest sibling. It stops short of covering when-not to use it against the many other list_* tools, so it is clear context rather than full when/when-not guidance.

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

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

Resources

Need Help?