Skip to main content
Glama

Kubeez

list_assets

Read-onlyIdempotent

Scope: generate:media. List the user's persistent Asset Library — named, reusable images / videos / audio stored in their private R2 bucket. Each entry has a stable name (e.g. tesote-logo), an id, kind (image|video|audio), size_bytes, and a freshly signed CDN url valid for 1 hour. USE WHEN: the user references a brand asset, logo, recurring face / voice / song clip, or says 'use my logo / my photo / my track' — before asking them to re-upload, check here first; their library may already have it. REFERENCING IN GENERATIONS: pass the url field of any matching asset directly into generate_media as a source_media_urls value — the URL is a public signed CDN link the model can fetch. Also returns quota_bytes / used_bytes so you can warn the user before calling manage_library(kind='asset', action='add', ...) if they're near the cap (default 50 MB). TEAM SEATS: active team members also see their team's shared assets merged into assets — those rows carry shared: true, owner_user_id, and uploaded_by {user_id, username}; a slim team block reports the team pool's quota_bytes / used_bytes. KLING ELEMENTS: when the user has saved any, a kling_elements block lists them — named reference bundles (name, description, image_urls, video_urls) they built in the app to keep a person, product or place consistent on kling-3-0-* models. Check here too before asking for a reference photo; pass any of their URLs into generate_media as source_media_urls values. Saved Kling 4.0 subjects and voices come back separately under kling_4_elements / kling_4_voices, already shaped for generate_media's elements / voices arguments on kling-4-0-* models (mention each as @name; Kling 4.0 Flash takes the elements but not the voices). Save new ones with manage_library(kind='kling_element' | 'kling_voice').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description still adds real behavioral context the annotations cannot: signed CDN URLs valid for 1 hour, quota/used byte reporting with a 50 MB default, team assets merged in with shared/owner_user_id/uploaded_by, and separate kling_4_elements / kling_4_voices blocks. What holds it below a 4-5 is that the level of detail is uneven and partly drifts into describing downstream tools rather than this one's own behavior.

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?

Well front-loaded: scope, then what it returns, then USE WHEN, then referencing, then the team and Kling variants. The KLING ELEMENTS paragraph runs long and the Kling 4.0 Flash caveat is dense, but nearly every sentence carries operational information rather than filler.

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?

An output schema exists, so return values needn't be explained, yet the description goes further by describing field semantics, URL expiry, and how to feed returned URLs into generate_media's source_media_urls/elements/voices. For a zero-argument listing tool with team and Kling variants, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema imposes no burden and the baseline is 4. The description spends its parameter-adjacent effort on the response shape (name, id, kind, size_bytes, url) and on which fields to forward elsewhere, which is useful but belongs to returns rather than inputs.

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?

Opens with an explicit scope tag and a precise verb+resource: list the user's persistent Asset Library of named reusable media in their private R2 bucket. It distinguishes itself from write-path siblings by pointing at manage_library(kind='asset', action='add', ...) for saving and generate_media for consumption, so an agent can tell what this tool is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

A dedicated USE WHEN block gives the trigger conditions (user references a brand asset, logo, recurring face/voice/song clip, 'use my logo') and an explicit ordering rule: check here before asking them to re-upload. It also names the alternative for the write side and the condition (near quota cap) under which to warn before calling it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources