VideoGen

List entities

list_entities

Read-onlyIdempotent

List built-in actors, products, visual styles, and slideshow themes plus team entities (including brands, locations, and props). Built-in rows have isBuiltIn true and cannot be updated or archived. Filter with entityType when you only need one kind.

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_entities"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of items to return.
`cursor`	No	Pagination cursor from a previous response's `nextCursor`.
`entityType`	No	When set, only return entities of this type.

Output Schema

Name	Required	Description
`hasMore`	Yes	Whether another page is available.
`entities`	Yes	Entities visible to the API key.
`nextCursor`	Yes	Cursor for the next page, or null.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

changedOutput schema / properties / entities / items / properties / actorConfig / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "hasAvatarPresenter": {
-        "description": "True when the actor has an image reference usable for avatar generation.",
-        "type": "boolean"
-      },
-      "hasVoice": {
-        "description": "True when the actor has a configured voice.",
-        "type": "boolean"
-      },
-      "voiceDisplayName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Configured voice display name when set."
-      }
-    },
-    "required": [
-      "hasVoice",
-      "hasAvatarPresenter"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "hasAvatarPresenter": {
+        "description": "True when the actor has an image reference usable for avatar generation.",
+        "type": "boolean"
+      },
+      "hasVoice": {
+        "description": "True when the actor has a configured voice.",
+        "type": "boolean"
+      },
+      "voiceDisplayName": {
+        "description": "Configured voice display name when set.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "hasVoice",
+      "hasAvatarPresenter"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / nextCursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed7 schema fields changedOct 16, 2026

changedInput schema / properties / entityType / enum

Previous value: -[
-  "ACTOR",
-  "PRODUCT",
-  "VISUAL_STYLE",
-  "SLIDESHOW_THEME"
-]New value: +[
+  "ACTOR",
+  "PRODUCT",
+  "VISUAL_STYLE",
+  "SLIDESHOW_THEME",
+  "BRAND",
+  "LOCATION",
+  "PROP"
+]

changedOutput schema / properties / entities / items / description

Previous value: -"A reusable actor, product, visual style, or slideshow theme entity."New value: +"A reusable actor, product, visual style, slideshow theme, brand, location, or prop entity."

addedOutput schema / properties / entities / items / properties / brandConfig

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "colors": {
+          "description": "Color guidance.",
+          "type": "string"
+        },
+        "fonts": {
+          "description": "Font guidance.",
+          "type": "string"
+        },
+        "writingStyle": {
+          "description": "Voice and tone for copy.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "fonts",
+        "colors",
+        "writingStyle"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Brand guidance for BRAND entities; null for other types."
+}

changedOutput schema / properties / entities / items / properties / entityType / description

Previous value: -"ACTOR, PRODUCT, VISUAL_STYLE, or SLIDESHOW_THEME."New value: +"ACTOR, PRODUCT, VISUAL_STYLE, SLIDESHOW_THEME, BRAND, LOCATION, or PROP."

changedOutput schema / properties / entities / items / properties / entityType / enum

Previous value: -[
-  "ACTOR",
-  "PRODUCT",
-  "VISUAL_STYLE",
-  "SLIDESHOW_THEME"
-]New value: +[
+  "ACTOR",
+  "PRODUCT",
+  "VISUAL_STYLE",
+  "SLIDESHOW_THEME",
+  "BRAND",
+  "LOCATION",
+  "PROP"
+]

addedOutput schema / properties / entities / items / properties / references / items / properties / role

Added value: +{
+  "description": "REFERENCE for generation and thumbnails; BRAND_LOGO / BRAND_STYLE_GUIDE for a brand's logo and style guide.",
+  "enum": [
+    "REFERENCE",
+    "BRAND_LOGO",
+    "BRAND_STYLE_GUIDE"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / entities / items / properties / references / items / required

Previous value: -[
-  "fileId",
-  "description",
-  "isDefault"
-]New value: +[
+  "fileId",
+  "description",
+  "role",
+  "isDefault"
+]

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that built-in rows carry isBuiltIn true and cannot be updated or archived, which explains a behavioral constraint the agent would otherwise discover only through failure. Pagination behavior is left to the schema's cursor field.

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?

Three tight sentences with no filler, and the resource enumeration is front-loaded ahead of the behavioral caveat and the filtering hint. Slightly dense in the first sentence, but every clause carries information an agent needs.

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 a full output schema, rich annotations and complete parameter documentation, the description only needs to cover scope and built-in immutability, both of which it does. Nothing essential for correct invocation is missing, though a pointer to get_entity for single-item lookup would round it out.

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 limit, cursor and entityType are all documented in the schema itself. The description reinforces entityType's filtering purpose but adds no syntax, format or edge-case detail beyond that, so the baseline 3 applies.

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 uses the specific verb 'List' and enumerates the exact resource classes returned: built-in actors, products, visual styles, slideshow themes, plus team entities (brands, locations, props). This makes it clearly distinguishable from get_entity and create_entity, which operate on a single entity.

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

Usage Guidelines3/5

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

One concrete usage hint is given ('Filter with entityType when you only need one kind'), which tells the agent when to narrow results. However, there is no guidance on when to choose this over get_entity for a known ID, nor any prerequisites or exclusions, leaving the when-not-to-use case implicit.

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

All VideoGen 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.