Skip to main content
Glama

Run Any Replicate Model

replicate_run_model

Run any model from the Replicate catalog by its owner/name identifier. Supports all categories including embeddings, segmentation, depth estimation, and more.

Instructions

Generic escape hatch: run ANY model in the Replicate catalog by its "owner/name" identifier. This tool gives Claude access to the entire Replicate model catalog — anything not covered by the curated specialised tools (image, video, audio, speech, chat, vision, upscale, remove-bg) can be reached from here.

DISPLAY REQUIREMENT — if the result includes image URLs, paste ONE of the embed blocks the tool prints (iframe / / markdown — try in order) verbatim in your reply so the image renders inline in the chat.

Use this for any category WITHOUT a curated specialised tool, including but not limited to:

  • Embeddings (sentence-transformers, BGE, Jina)

  • Segmentation (SAM, Segment Anything)

  • Depth estimation (MiDaS, ZoeDepth, Marigold)

  • Inpainting / outpainting (LaMa, Stable Diffusion Inpaint, controlnet-inpaint)

  • ControlNet variants (canny, depth, openpose, normal-map)

  • Face / pose / hand detection (insightface, mediapipe, etc.)

  • 3D generation (TripoSR, Wonder3D, InstantMesh)

  • Audio-to-text / speech recognition (whisper, Distil-Whisper)

  • Audio separation / stem splitting (Demucs, MDX)

  • Style transfer, colourisation, deblurring, denoising

  • Code completion / instruction-tuned code models (CodeLlama, DeepSeek-Coder)

  • Music continuation / source separation

  • ANY newly released model not yet in the curated registries

Workflow:

  1. (Optional) Call replicate_search_models to discover models by keyword (e.g. "image segmentation", "speech to text").

  2. (Recommended) Call replicate_get_model_schema with "owner/name" to inspect required inputs.

  3. Call this tool with the model id and an input object matching that schema.

Args:

  • model (string): "owner/name" (latest official version) or "owner/name:version_hash" (pinned).

  • input (object): Model-specific input parameters.

  • download (boolean, default true): Download outputs locally.

  • timeout_ms: Default 300000.

Returns: PredictionResult.

Examples:

  • Upscale an image: model="nightmareai/real-esrgan", input={"image": "https://example.com/in.png", "scale": 4}

  • Remove background: model="lucataco/remove-bg", input={"image": ""}

  • Run an LLM (output is text, not a file, so local_paths will be empty): model="meta/meta-llama-3-70b-instruct", input={"prompt": "Explain quantum entanglement in two sentences."}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesModel input parameters as a JSON object. Use replicate_get_model_schema first if unsure what a model accepts.
modelYesReplicate model identifier. Either "owner/name" (uses latest official version) or "owner/name:version_hash" (pins a specific version). Examples: "black-forest-labs/flux-schnell", "meta/meta-llama-3-70b-instruct".
downloadNoWhether to download the generated files locally. Default true. When false, only Replicate URLs are returned (URLs expire after ~24h).
timeout_msNoMax ms to wait for the prediction. If exceeded, returns the prediction ID so you can poll via replicate_get_prediction. Default: 300000 (5min).
Behavior4/5

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

Annotations already indicate openWorldHint=true and destructiveHint=false. Description adds value by explaining timeout behavior (returns prediction ID if exceeded), download default and effect, and that it runs any model. No contradictions.

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?

Description is lengthy but well-structured with sections, workflow, examples, and display requirement. Every sentence serves a purpose. Minor redundancy could be trimmed, but overall it is organized and front-loaded with key points.

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

Completeness5/5

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

Given the tool's generality (no output schema), the description thoroughly covers return value (PredictionResult), behavior for images, timeout handling, and workflow. It is complete enough for an agent to use correctly without additional cues.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds rich context: for model parameter explains format and version pinning; for input recommends using get_model_schema first; for download explains when to use false; for timeout explains max and behavior. This significantly aids correct invocation.

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 clearly states the tool runs 'ANY model' in the Replicate catalog by identifier, distinguishing it from curated specialized tools. It provides a specific verb and resource, and directly differentiates from siblings by listing categories without curated tools.

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

Usage Guidelines5/5

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

Explicit guidance on when to use (categories without curated tool) and when not to use (prefer curated tools). Recommends a workflow: search, get schema, then run. Provides examples of appropriate use cases and clear alternatives.

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/sena-labs/replicate-mcp-server'

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