listGeneratedImages
Retrieve a list of all images generated by the video creation server, enabling review and management of outputs.
Instructions
List all generated images
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve a list of all images generated by the video creation server, enabling review and management of outputs.
List all generated images
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose read-only nature, auth requirements, or any side effects. Simply states 'list all', offering no behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise at one sentence, no wasted words. Could be slightly improved by front-loading key info, but currently adequate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple list tool with no params or output schema; however, lacks any mention of pagination or ordering, which may be necessary for completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters; schema coverage is 100%. Description adds no parameter info, but none is needed. Baseline 4 is appropriate for no-param tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb (list) and resource (generated images), distinguishing from siblings like getImage (single) and generateImage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives; no mention of filtering, pagination, or context such as if the list is all images or scoped to a user.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mario-andreschak/mcp-veo2'
If you have feedback or need assistance with the MCP directory API, please join our Discord server