Skip to main content
Glama

replicate_create_prediction

Create a prediction to run a Replicate model with input parameters. Specify model version or owner/name, and optionally set webhook or streaming.

Instructions

Run a Replicate model by creating a prediction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_tokenYes
versionNoModel version ID (use this OR model)
modelNoModel as owner/name or owner/name:version (use this OR version)
inputYesModel input parameters as JSON object or string
webhookNo
streamNo
Behavior2/5

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

No annotations are provided, and the description fails to mention critical behavioral traits: predictions are asynchronous, require polling, may incur costs, and have rate limits. The description 'create a prediction' is too vague for a computational tool.

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

Conciseness3/5

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

The description is a single sentence with no waste, but it is overly minimal. It is not structured with bullet points or sections, making it less scannable. It earns a 3 for being concise but not well-structured.

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 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return value, the asynchronous behavior, error scenarios, or how to handle the prediction ID. A more complete description is needed for a creation tool that triggers background processing.

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

Parameters2/5

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

The description adds no parameter semantics beyond the input schema. With 50% schema description coverage, the description should compensate for undocumented parameters like webhook and stream, but it does not.

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 uses a specific verb 'Run' and clearly identifies the resource 'a Replicate model' and the action 'creating a prediction'. It distinguishes this tool from siblings like replicate_get_prediction and replicate_cancel_prediction by focusing on creation.

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?

No guidance on when to use this tool vs alternatives such as replicate_get_prediction for checking results. The description lacks any context about prerequisites or comparison with sibling tools.

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/malamutemayhem/unclick'

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