Skip to main content
Glama

put-models-by-model-id

Update an existing AI model's configuration, including name, type, parameters, and training settings, by specifying its model ID.

Instructions

Update the given modelId

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalAssetsNoIf set to true, returns the original asset without transformation
modelIdYesThe model's `modelId` to update
negativePromptEmbeddingNoAdd a negative prompt embedding to every model's generation
thumbnailNoThe AssetId of the image you want to use as a thumbnail for the model (example: "asset_GTrL3mq4SXWyMxkOHRxlpw"). Set to null to unset the thumbnail
conceptsNo
classSlugNoThe slug of the class you want to use (ex: "characters-npcs-mobs-characters"). Set to null to unset the class
nameNoThe model's name (ex: "Cinematic Realism"). If not set, the model's name will be automatically generated when starting training based on training data.
epochNoThe epoch of the model. Only available for flux.1-lora and flux.1-kontext-lora based models. The epoch can only be set if the model has epochs and is in status "trained". The default epoch (if not set) is the final model epoch (latest). Set to null to unset the epoch.
promptEmbeddingNoAdd a prompt embedding to every model's generation
shortDescriptionNoThe model's short description (ex: "This model generates highly detailed cinematic scenes."). If not set, the model's short description will be automatically generated when starting training based on training data.
typeNoThe model's type (ex: "flux.1-lora"). The type can only be changed if the model has the "new" status.
parametersNo
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to indicate that this is a mutation operation (implied by 'Update'), specify required permissions, describe side effects (e.g., overwriting existing settings), mention rate limits, or detail the response format. For a complex update tool with 12 parameters, this lack of transparency is critical.

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

Conciseness2/5

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

The description is a single under-specified sentence that fails to convey essential information. While concise, it is not appropriately sized for a tool with 12 parameters and complex functionality. It lacks front-loaded critical details and does not earn its place as a helpful description.

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

Completeness1/5

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

Given the tool's complexity (12 parameters, nested objects, no output schema, and no annotations), the description is severely incomplete. It does not explain the update scope, behavioral implications, or usage context. For a mutation tool with extensive configuration options, this minimal description is inadequate and fails to provide necessary operational context.

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 (83%), providing detailed documentation for most parameters. The description adds no parameter-specific information beyond implying the 'modelId' is updated. Since the schema carries the burden, the baseline score of 3 is appropriate, though the description does not compensate for the remaining 17% coverage gap or clarify parameter interactions.

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

Purpose2/5

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

The description 'Update the given `modelId`' is a tautology that restates the tool name without specifying what is being updated. It lacks a clear verb-resource combination (e.g., 'Update model metadata and training parameters') and does not distinguish this tool from sibling PUT tools like 'put-models-by-collection-id' or 'put-models-train-by-model-id'. The purpose is vague and under-specified.

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

Usage Guidelines1/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 does not mention prerequisites (e.g., model status requirements), exclusions, or compare it to sibling tools like 'put-models-train-by-model-id' (for training actions) or 'post-models' (for creation). This leaves the agent without context for tool selection.

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