Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Browse a connected creative account

list_connected_assets
Read-onlyIdempotent

List (or search, with query) the images and videos in the organization's own connected creative account: magnific (Freepik (Magnific)), higgsfield (Higgsfield), runway (Runway), ideogram (Ideogram), heygen (HeyGen). Returns each asset's id, title, kind and thumbnail, for import_connected_asset. Needs the account to be connected already — connecting is a sign-in the owner does in Settings → Creative Accounts; it cannot be done from a conversation.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 30)
queryNoSearch words; omit for recent assets
providerYesWhich connected account
user_goalNoOptional: 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.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

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, so the description's added value is the hard precondition (account must be connected out-of-band) and the return shape (id, title, kind, thumbnail). That is real behavioral context beyond the annotations; pagination/limit behavior is left to the schema.

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?

A single dense paragraph that front-loads the action and the provider list, then the return fields, then the precondition. The provider list with duplicate display names is slightly verbose but earns its place for enum mapping.

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 four returned fields; the mutation-adjacent follow-up (import_connected_asset) and the connection prerequisite are both covered. Only ordering/pagination semantics are unaddressed, a minor gap.

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%, so provider, query, limit, and user_goal are already documented. The description only adds that supplying `query` shifts the call into search mode, which is marginal beyond the schema's 'Search words; omit for recent assets'.

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?

Specific verb (list/search) plus a precisely scoped resource: 'the images and videos in the organization's own connected creative account.' It enumerates the exact providers and distinguishes itself from brand-library or creation-search siblings by that scoping.

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?

Explicitly routes to the downstream sibling ('for import_connected_asset') and states the prerequisite that the account must already be connected, including that connecting is a Settings sign-in that cannot happen in a conversation. It stops short of naming when to prefer a different listing tool instead.

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

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