Every tool the Glossi MCP server offers an agent, grouped by area, with what it does and whether it reads, changes or deletes.
Every tool your agent can call once it is connected to Glossi. Your agent reads the full description and arguments of each tool when it connects, so you never call these yourself. This page is for knowing what to ask for and what the agent will ask you before doing.
Enterprise. Agent access is available on Enterprise. It uses the same plan gate as REST API keys.
Kind comes from the tool's own annotations:
read only fetches data, or shows an in-chat panel.
write creates or changes something in your workspace.
destructive deletes, replaces or overwrites something. The agent names what will go and asks you before it calls one.
Every tool takes an optional workspaceId. Leave it out and the agent works in your default workspace, and says so. Tools that spend usage say so below; the agent confirms before large batches, and get_usage reports what is left as a percentage.
Workspaces you can work in, and which is the default.
get_usage
read
How much of this month's usage is left, as a percentage, and when it renews.
list_projects
read
Projects in the workspace, newest first.
create_project
write
Build a project from existing models, optionally with a template's scene setup. Projects an agent creates are marked with an agent source in the app.
rename_project
write
Give a project a new name.
delete_project
destructive
Delete a project. Its renders stay. Refused while a template made from it exists or a Studio has it open.
list_templates
read
Saved scene setups (lighting, backdrop, cameras), yours and Glossi's public ones.
save_project_as_template
write
Save a project's scene as a new template, so other models can be built into the same setup. Not available on the legacy Starter plan.
update_template_from_project
write
Save a new version of a template from a project. Earlier versions are kept.
apply_template_to_project
destructive
Replace a project's scene with a template's. The models stay; the old scene doesn't. Refused while the project is open in a Studio, where studio_apply_template does it in place.
The upload panels only exist in Claude.ai and Claude Desktop. In a client with a shell, the agent uploads from disk with the create_* and confirm_* tools instead. Models and props can be up to 3 GB; anything Glossi fetches from a link can be up to 1 GB.
Tool
Kind
What it does
upload_model
read
Shows an in-chat upload panel for one model, many, or a whole folder.
upload_props, upload_decals
read
The same panel for props (3D files) or decals (images).
upload_materials
read
The same panel for a folder of PBR textures, loose or zipped, with a review step before upload.
import_model
write
Add a model from a public download link. Glossi fetches it server-side.
create_model_upload
write
Start an upload from disk: returns a modelId and a URL to PUT the file to.
confirm_model_upload
write
Tell Glossi the file is uploaded; processing starts.
start_model_multipart_upload
write
Split a large upload into parts that resume if interrupted.
get_model_upload_part_urls
read
Upload URLs for parts of a multipart upload.
complete_model_multipart_upload
write
Assemble the uploaded parts; processing starts.
abort_model_multipart_upload
destructive
Discard the parts uploaded so far.
wait_for_models
read
Wait until models are READY or APPROVED, or have failed.
create_library_uploads
write
Start a batch upload: 3D files as models or props, images as decals, PNG or JPEG backgrounds as backplates.
confirm_library_uploads
write
Confirm the batch is uploaded; models and props start converting.
wait_for_props
read
Wait until props finish converting.
plan_material_import
read
Group a folder's texture images into PBR materials by file name.
create_material_upload
write
Start one PBR material from its texture files.
confirm_material_upload
write
Confirm the textures are uploaded. Optionally generate missing maps (spends usage; the agent asks you the material type and whether it has transparency first) or upscale the base colour.
Find materials by name, colour or category, in your workspace or the Glossi catalog.
find_material
read
Find a described material ("purple suede") in your library, the Glossi catalog, then Poly Haven and ambientCG. Says whether to use one as it is, add one, or generate one.
add_material
write
Add a material to your library: a catalog material, a recoloured library or catalog material, or an imported online scan. Doesn't spend usage.
generate_material
write
Create a PBR material from a description, a reference photo, or both. Spends usage.
upload_material_reference
read
Shows an in-chat upload panel for one photo of a surface, to generate a material from.
create_material_reference_upload
write
Upload URL for a local reference photo, for generate_material or sample_photo_colors.
sample_photo_colors
read
Measure the colour of each zone of a reference photo, so find_material matches it exactly.
recolor_material
write
Add a material that keeps another's textures and finish, tinted a new colour. The source is a library material or a fabric region on a model. Best on a near-white fabric.
wait_for_materials
read
Wait until materials are ready.
swap_material
write
Replace materials on models by slot name, producing new model variants.
get_material_swap_status
read
Progress of a swap batch and the variants it produced.
list_design_materials
read
Design materials: SVG designs whose colour slots a variant can recolour.
list_workspace_colors
read
The workspace colour library, with hex, CMYK and Pantone, for a design's slots.
Whether the workspace can create models from photos, and how they are paid.
generate_model_from_photos
write
Start a 3D model from 1 to 6 product photos. Spends usage when it starts, unless your workspace has models included or priced per model, in which case a model is paid when you approve it.
wait_for_model_generation
read
Progress of a generation; when ready, preview views to review; once added, the modelId.
list_model_generations
read
Your generations, newest first.
approve_generated_model
write
Add a reviewed model to the library. Pays for it when your workspace buys models per model.
decline_generated_model
destructive
Throw a reviewed model away. Usage it spent is kept.
See Model prep API for arguments and the matching REST endpoints.
Tool
Kind
What it does
get_model_prep_offer
read
What a full prep of the model costs, the changes included, and whether it is paid at the start or on keep.
prepare_model
write
Split a model into parts, name its parts and finishes, redo its UVs. Label, UV and material passes spend usage. A full prep (splitting into parts) is a one-off purchase charged to the workspace's saved card; the agent tells you the price and asks first.
match_variant_to_photo
write
Make a variant that looks like photos of the product: regroups the parts by the colour zones in the photos and picks a library material for each. Spends usage.
get_model_prep
read
Progress of a run; when ready, what changed and what the prep wasn't sure of.
list_model_preps
read
A model's runs, newest first.
retry_model_prep
write
Change one area of a result from your feedback and screenshots. May ask a question first. A change to a usage run spends usage.
keep_model_prep
write
Make the result the model's current version. Pays for a full prep that wasn't paid when it started.
Enterprise. Automations are available on Enterprise. Only one automation can be active in a workspace at a time.
A new automation is saved paused. Your agent can't sign in to Google Drive, OneDrive or AEM for you, and credentials never pass through it: a step that needs one of those accounts is saved unconnected, and the agent gives you a link to connect it in Glossi. The matching REST endpoints are under /api/v1/pipelines.
Tool
Kind
What it does
list_automations
read
Your automations, their trigger, the steps they run and whether they're ready.
get_automation_options
read
Every trigger and step, which can follow which, and the connectors.
get_automation
read
One automation's steps and settings, and anything left to set up in Glossi. Credentials are never shown.
create_automation
write
Build an automation, saved paused. An invalid chain is refused with what's wrong.
update_automation
destructive
Change the name, steps or settings, or activate or pause it. Changing an active automation's steps needs your yes; activating one lets it spend usage unattended and pauses your other active automation.
delete_automation
destructive
Delete an automation and its job history. What it made is kept unless you ask. Refused while jobs are running.
run_automation
write
Run an automation now, like Run once. A Manual automation can run on models you choose. Pauses your other active automation while it runs. Spends usage.
get_automation_run
read
Progress of a run: each model's steps, renders, outputs and errors.
These tools find the Studio to work on, collect results, and save or render it. See Control the Studio from an agent for how live and cloud sessions work.
Tool
Kind
What it does
list_studio_sessions
read
Your open Studio sessions in the workspace, live or in the cloud, and the project each has loaded.
get_studio_selection
read
What you have selected in the Studio: photo or video mode, the current shot or clip, and what the right panel shows.
open_studio_session
write
Load a project into a Studio in the cloud, with nobody watching. Takes 5 to 15 minutes to start and uses Studio time while it runs. One per workspace.
wait_for_studio_session
read
Wait for a cloud session to reach its next stage, until it is READY or FAILED.
close_studio_session
write
Save the project and end a cloud session.
save_studio_session
write
Save the project as the Studio has it now.
render_studio_session
write
Save, then render the shots, clips and variants as the Studio has them now, or only the ones named. Spends usage.
studio_prompt
write
Hand one instruction to the Studio's own Assistant, which plans and makes the change. Spends usage like a prompt in the Studio panel.
studio_batch
destructive
Up to 25 studio_ calls in one request, run in order. Marked destructive because a batch can include deletes; one that does is refused until you have said yes.
wait_for_studio_call
read
Collect one change that was still running, or was sent without waiting.
wait_for_studio_calls
read
Collect up to 50 changes sent without waiting.
list_studio_call_group
read
The changes in one group, in order, with each one's status and timing.
list_studio_history
read
Recent groups of changes, newest first: label, who made them (you, the Assistant or an agent), when, and what they touched.
undo_studio_group
write
Revert one earlier change by an agent or the Assistant. Refused when a later change touched the same part of the scene.
upload_studio_reference
read
Shows an in-chat upload panel for one photo for the Studio to match, such as lighting to copy.
Every tool below starts with studio_ and acts on a Studio session: the one you have open, or a cloud session. Each takes an optional sessionId, plus wait, group and label (see How changes run).
The clips in the timeline, and one clip's framing and lens.
studio_add_clip, studio_edit_clip
write
Add and edit video clips.
studio_delete_clip
destructive
Delete a clip.
studio_link_clip_to_bookmark
write
Start a clip from a saved shot, or unlink it. Undo doesn't reverse it.
studio_set_clip_product_visibility
write
Leave a product out of one clip, or show it again.
studio_preview_clip
read
A clip's motion as 3 to 24 evenly spaced frames (4 by default), or at exact times. The clip is scrubbed, not played, and the Studio goes back as it was.
studio_animate_camera
write
Generate a camera move for a clip from a description. Spends usage.
studio_animate_product
write
Generate product motion for a clip, such as an exploded view or a spin. Spends usage.
studio_append_product_animation
write
Add one generated motion on top of a clip's existing product motion. Spends usage.
studio_animate_lights
write
Swing, fade or push the whole light setup over a clip.
Replace the scene with a template's backdrop, lighting, shots, clips and props, keeping the products. The project is saved first and reloads, which can take a few minutes.
studio_undo, studio_redo
write
Undo or redo the newest change in the Studio's history, like the Studio's own buttons.