Rawa

List creatives

list_creatives

Read-onlyIdempotent

The brand's generated and uploaded images, videos and SVGs, newest first, with their names and media URLs. Pages with nextCursor. An image the user pasted or attached in the chat is not here until they upload it through request_image_upload.

Input Schema

Name	Required	Description
`limit`	No	How many to return. Defaults to 20.
`cursor`	No	nextCursor from the previous page.
`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.
`assetTypes`	No
`favoritesOnly`	No
`includeImages`	No	Also show the pictures themselves, for the first 6 of the page. Off by default: ask for it when the user wants to look at the creatives rather than read about them.

Output Schema

Name	Required	Description	Default
`media`	No
`creatives`	Yes
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields 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."

changedInput schema / properties / includeImages / description

Previous value: -"Also show the pictures themselves, for the first 3 of the page. Off by default: ask for it when the user wants to look at the creatives rather than read about them."New value: +"Also show the pictures themselves, for the first 6 of the page. Off by default: ask for it when the user wants to look at the creatives rather than read about them."

addedOutput schema / properties / media / items / properties / previewUrl

Added value: +{
+  "description": "A small WebP of it to look at; url is the full size to hand over.",
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds what they cannot: result ordering (newest first), the shape of each item (name plus media URL), cursor-based paging, and the pre-upload visibility caveat. Minor gap: it never says the listing is brand-scoped/requires a brand context beyond the brandId param.

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?

Two sentences, front-loaded with what the tool returns and followed by the one behavioral caveat an agent would otherwise get wrong. No restatement of the title and no filler.

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?

With six optional parameters, an output schema, and rich annotations, the description covers the essentials: scope, ordering, paging, and the notable exclusion. The remaining shortfall is guidance on the two filter parameters (assetTypes, favoritesOnly) that an agent would need to use the tool fully.

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 67%, above the point where the schema alone suffices but below full coverage. The description's mention of images/videos/SVGs loosely maps to assetTypes, but favoritesOnly and assetTypes have no description in the schema and get no explanation here, so the description doesn't compensate for the documented gaps.

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 verb ('list') and resource ('the brand's generated and uploaded images, videos and SVGs') are stated concretely, along with ordering ('newest first') and the fields returned ('names and media URLs'). What's missing is differentiation from near-siblings in the toolset such as search_library, show_creatives and get_creative, so an agent still has to guess which listing tool to pick.

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?

The second sentence gives an explicit exclusion plus an alternative path: a pasted or attached image won't appear here until it goes through request_image_upload. That is real when-not guidance routing to a named sibling, but it only covers that one edge case; there is no guidance on when to prefer this over search_library or get_creative.

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?