Create a Raven creative generation job for image, video, 3D, audio, campaign, or analysis. Returns a brand-aware provider payload. If execute=true and RAVEN_CREATIVE_RUNNER is configured, Raven submits the job to that local runner.
AI agents invoke create_generation_job to trigger actions in Raven. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Raven model slot or external provider model ID. |
preset | string | — | Preset ID from list_creative_presets. |
prompt | string | Yes | Creative request. |
channel | string | — | Target channel, e.g. TikTok, YouTube Shorts, blog, marketplace. |
execute | boolean | — | Submit through RAVEN_CREATIVE_RUNNER now. Default false. |
quality | string | — | Requested quality tier. |
provider | string | — | Provider label for the downstream runner. |
objective | string | — | Business or audience goal. |
media_type | string | Yes | Output type. |
aspect_ratio | string | — | Target aspect ratio, e.g. 1:1, 16:9, 9:16. |
output_count | integer | — | Number of variants to request. |
brand_profile_id | string | — | Local Raven brand profile ID. |
Parameters from the server's own tool schema.
This tool triggers external operations (submitting jobs to a local runner) that depend on arguments. When execute=true, it actively dispatches work to an external system, making it Execute rather than Write.
From the tool's definition 'Create a Raven creative generation job' and 'If execute=true and RAVEN_CREATIVE_RUNNER is configured, Raven submits the job to that local runner'
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
Create a Raven creative generation job for image, video, 3D, audio, campaign, or analysis. Returns a brand-aware provider payload. If execute=true and RAVEN_CREATIVE_RUNNER is configured, Raven submits the job to that local runner. It is categorised as a Execute tool in the Raven MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
create_generation_job accepts 12 parameters: model, preset, prompt, channel, execute, quality, provider, objective, media_type, aspect_ratio, output_count, brand_profile_id. Required: prompt, media_type. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for create_generation_job: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Raven. Nothing to install.
create_generation_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_generation_job rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create_generation_job. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create_generation_job is provided by the Raven MCP server (raven-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →