Skip to main content
Glama

post-models-get-bulk

Retrieve multiple AI models by their IDs from Scenario.com's generative AI platform, including details, settings, and training images.

Instructions

Get multiple models by their modelIds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalAssetsNoIf set to true, returns the original asset without transformation
settingsNoIf true, will return the settings: `promptEmbedding` and `negativePromptEmbedding`.
trainingImagesPreviewNoIf true will return the first 3 training images; otherwise returns the full training images. If `allTrainingImages` set to true, this parameter is ignored.
minimalNoIf true will return only the base details of the model (id, name, type) if true, all other parameters are ignored
thumbnailNoIf true will return the thumbnail, when no thumbnail is set, will try to fetch the first training image instead.
allTrainingImagesNoIf true will return all training images; otherwise returns only the first 3 training images. If `trainingImagesPreview` set to true, this parameter is ignored.
modelIdsNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's non-destructive, but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or response format. The description is minimal and lacks essential context for safe and effective use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence earns its place by specifying the operation and key input.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain the tool's role in the system, how it differs from siblings, what it returns, or any behavioral constraints. For a bulk retrieval tool with multiple configuration options, more context is needed to guide proper use.

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 high (86%), so the baseline is 3. The description mentions 'modelIds' as the key parameter, aligning with the schema, but adds no additional meaning beyond what's documented in the schema properties. It doesn't explain parameter interactions or provide usage examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('multiple models'), specifying the key identifier ('modelIds'). It distinguishes from individual model retrieval tools like 'get-models-by-model-id' by emphasizing bulk retrieval. However, it doesn't explicitly differentiate from other bulk operations like 'post-asset-get-bulk' or list operations like 'get-models'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'get-models' (which likely lists all models) or 'get-models-by-model-id' (for single models), nor does it specify prerequisites like authentication or rate limits. Usage context is implied but not articulated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pasie15/scenario.com-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server