Mondovo

List a brand's uploaded assets

list_brand_assets

Read-onlyIdempotent

The files uploaded to a brand's library — photos, logos, videos, documents — newest first, with ids and urls. Generated visuals, logos and films are list_creations.

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": {
      "brand_id": "<brand_id>"
    },
    "name": "list_brand_assets"
  }
}

Input Schema

Name	Required	Description
`type`	No
`limit`	No	Default 24.
`offset`	No
`search`	No	Words from the name.
`brand_id`	Yes	Brand workspace id from list_brands
`user_goal`	No	Optional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / user_goal

Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds real value beyond that by disclosing sort order (newest first) and what comes back (ids and urls). It says nothing about pagination behavior or total counts, which is the main remaining gap for a list endpoint.

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 short sentences, front-loaded with the resource definition and followed immediately by the disambiguation rule. Every clause carries information; nothing is repeated from the title or annotations.

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?

No output schema exists, and the description compensates by naming the returned fields (ids and urls) and ordering. With six parameters and no annotation gaps on safety, the definition is nearly sufficient, though filter and pagination semantics remain undocumented anywhere except partially in the schema.

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 67%, below the threshold where the schema alone suffices, and the description never mentions the type, limit, offset or search filters. The enumeration of file kinds loosely maps to the type enum but omits font and other, and gives no hint on limit defaults or search semantics. Baseline 3 for a partially documented schema.

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 resource (files uploaded to a brand's library), the object types covered (photos, logos, videos, documents), and the ordering (newest first). The second sentence explicitly carves out generated content to a sibling, so an agent can distinguish it from list_creations without opening any 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?

Clear routing rule: generated visuals, logos and films belong to list_creations, implying this tool is for uploaded/original files only. It does not address other plausible alternatives in the sibling set, notably search_brand_library and get_brand_asset, so the when-to-use map is incomplete but the primary ambiguity is resolved.

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

All Mondovo 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?