Skip to main content
Glama

VidGuy

by ai.vidguy
OverviewDiscussionsAdmin

List influencer vault assets

list_influencer_assets
Read-only

List the generated assets in an influencer's vault (on-camera stills, faceless slides, b-roll videos, portraits, the character sheet), newest first. Returns 10 by default in a compact form without generation prompts, plus roleCounts (every asset per role) so you know what exists before paging. Filter by role and page with offset. Thumbnails are attached. Roles: static_ugc = on-camera stills of the influencer (first frames for talking-head clips); faceless_broll = faceless lifestyle slides (no face; carousels and faceless posts); broll = b-roll VIDEO clips with the influencer in them (use as cutaways); character_sheet = identity reference sheet (a grid; never a video first frame); portrait = look previews and headshots (metadata.previewLayout 'lite_sheet' is a two-panel preview; never a first frame); candid_still = candid stills; generated = images/videos made in the influencer's chat; face_reference / full_body = uploaded identity references.

Input Schema

NameRequiredDescriptionDefault
roleNoOnly this role. See roleCounts for what the vault holds.
limitNoAssets per page (default 10). Prefer a role filter over a big page.
offsetNo
verboseNoInclude full metadata with each generation prompt (~2.5k characters per asset). Default false.
influencerIdYesInfluencer id from list_influencers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Assets per page (default 10). Prefer a role filter over a big page."
    • changedInput schema / properties / role / description
      Previous value: -"Filter by asset role (e.g. static_ugc, carousel_slide, character_sheet)"New value: +"Only this role. See roleCounts for what the vault holds."
    • addedInput schema / properties / role / enum
      Added value: +[
+  "static_ugc",
+  "faceless_broll",
+  "broll",
+  "character_sheet",
+  "portrait",
+  "candid_still",
+  "generated",
+  "face_reference",
+  "full_body"
+]
    • removedInput schema / properties / role / maxLength
      Removed value: -80
    • addedInput schema / properties / verbose
      Added value: +{
+  "description": "Include full metadata with each generation prompt (~2.5k characters per asset). Default false.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral detail beyond that: default page size (10), compact form omitting generation prompts, roleCounts output, thumbnails attached, and the verbose cost (~2.5k chars per asset). This is well beyond what the annotations supply.

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?

Front-loaded with purpose, return behavior, then a dense role glossary. The role enumeration is long, but each entry carries distinct selection semantics rather than filler. Slight density cost keeps it from a 5.

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 no output schema, the description carries the return-shape burden and does so: default count, compact vs verbose form, roleCounts, thumbnails, and pagination. For a 5-param listing tool this is complete enough to call correctly without further discovery.

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

Parameters5/5

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

Schema coverage is 80% (baseline 3), but the description goes further by explaining the semantics of nearly every role enum value and the practical consequence of paging and verbose. The role mapping in particular adds meaning the bare enum list does not carry.

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?

The description opens with a specific verb and resource ('List the generated assets in an influencer's vault') and immediately enumerates the asset kinds (stills, slides, b-roll, portraits, character sheet). This scoping distinguishes it from adjacent siblings like list_influencer_studio_images and list_videos, which cover different asset sources.

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?

It gives clear operating context: default return of 10, roleCounts provided 'so you know what exists before paging', and filter/page usage. Role entries even suggest intent ('use as cutaways'). However, it never names an alternative sibling or states when NOT to use this tool, so it stops short of explicit routing.

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

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