Skip to main content
Glama

generate task

generate_task
Destructive

Create one independent billable Studio task. For user-attached or local media in a host with native APIXO attachments, use reference_files with file_bindings. ChatGPT and native Codex connectors use this route. Pass the host-provided attachment or the absolute local path when the connector accepts paths. If the native attachment fails, ask the user to reattach it or supply a usable URL. Do not rehost a failed native attachment without an explicit user request. Put existing media URLs supplied or selected by the user in input. Choose the attachment route by capability. Use reference_files when the client provides native APIXO attachments, including ChatGPT and compatible Codex connectors. Otherwise, for user-selected files accessible to the client, automatically use upload_reference and the APIXO uploader when the client can run Node.js 22+ and reach APIXO. This applies to Claude Code, Cursor, Grok Bot, WorkBuddy, and other clients that meet those conditions. A request to use the selected files in APIXO is sufficient to start the upload; honor the client's execution permissions. Read the model schema and identify each destination URL field before uploading. Submit only confirmed URLs in the user's order. If file access or execution is unavailable, explain the limitation and ask for a usable direct link. Keep upload grants out of replies and show reference URLs only on request. Read list_models.defaults for the default model of this tool, then get_model_schema for the complete schema. generate_task requires model; shortcuts may omit it. Explicit model selects that public task model. Set the documented mode in input; no mode, model fields, defaults or voice choices are inferred or injected. Flat model parameters and legacy reference_images/reference_audio are not accepted. Backend validation is authoritative. Use session_title for a new topic, session_id to continue, and session_id plus base_run_id for a version. Preserve returned model/task_id/session_id/run_id/media_type. Never automatically resubmit or change model/session after rejection or an unconfirmed submission. In user-facing replies, omit technical identifiers by default, including user/profile IDs, task_id, session_id, run_id, base_run_id, voice_id, and file IDs. Retain the exact returned identifiers for tool arguments, task queries, session continuation, version appends, and voice reuse; never redact, regenerate, or guess these references. Show an identifier only when the user explicitly asks for it or a specific troubleshooting step requires that exact value, and show only the reference needed. Prefer plain-language status, model names, result previews/download links, and Studio links built from the returned session_id. This changes reply presentation only; tool result fields remain available for the workflow.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>",
      "model": "<model>"
    },
    "name": "generate_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesFollow get_model_schema.schema for the original model parameters, including nested objects and arrays. For files bound through reference_files, leave the bound URL fields absent from input. Use direct media URL fields for existing links supplied or selected by the user. Do not mix media URLs with reference_files. Routing, identity and session overrides are not model inputs.
modelYes
session_idNoUse a returned or user-provided Studio session ID to add related work to that project. Never guess a session ID.
base_run_idNoTo revise a specific work, pass its returned run_id and the same session_id. Omit to create an independent work in the project.
file_bindingsNoUse paths declared in schema.mcp.attachments. Replace [] with an explicit input array index, e.g. elements[0].image_urls; provide parent objects and their metadata in input. Bind every file once using zero-based file_indices in intended order. Never overwrite direct URLs or guess fields or ordering.
session_titleNoRequired for a new Studio topic: 1-255 characters after trimming. Ignored when session_id is provided.
reference_filesNoUse this field for attached or local media when the host provides native APIXO attachment support. Use the host-provided files or absolute local paths when the connector accepts them, in the intended order. Use file_bindings to select model fields. Do not re-upload a failed native attachment without the user's explicit request. file_id is metadata. Use temporary download URLs only for this call and pass only known file metadata.

Output Schema

NameRequiredDescriptionDefault
errorYes
modelYes
stateYes
run_idNo
task_idYes
progressYes
voice_idYes
created_atYes
media_typeYes
session_idNo
completed_atYes
preview_urlsYes
text_outputsNo
download_urlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / input / description
      Previous value: -"Follow the complete get_model_schema.schema for model parameters, including nested objects and arrays. Values pass unchanged to backend validation; no plugin field or mode whitelist. Use direct media URLs or reference_files with explicit file_bindings, without mixing them. Routing, identity and session overrides are not model inputs. Metadata does not prove content or access."New value: +"Follow get_model_schema.schema for the original model parameters, including nested objects and arrays. For files bound through reference_files, leave the bound URL fields absent from input. Use direct media URL fields for existing links supplied or selected by the user. Do not mix media URLs with reference_files. Routing, identity and session overrides are not model inputs."
    • changedInput schema / properties / reference_files / description
      Previous value: -"ChatGPT files in original order. file_id is metadata, never a URL or permission proof. Temporary download URLs are used only in this call. Do not invent MIME, byte size, dimensions or duration."New value: +"Use this field for attached or local media when the host provides native APIXO attachment support. Use the host-provided files or absolute local paths when the connector accepts them, in the intended order. Use file_bindings to select model fields. Do not re-upload a failed native attachment without the user's explicit request. file_id is metadata. Use temporary download URLs only for this call and pass only known file metadata."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool as destructive and non-idempotent; the description adds that tasks are billable, that backend validation is authoritative, and that rejected submissions must not be auto-resubmitted. It also explains identifier handling and upload-grant secrecy, though it does not spell out permissions or exactly what side effects 'destructive' entails.

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 heavily repetitive, especially around attachment routing (reference_files vs upload_reference is restated several times), and it includes reply-presentation rules that are not needed to invoke the tool. The opening is front-loaded, but the overall length is excessive for a tool definition.

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?

For a complex, schema-rich, destructive creation tool with an output schema, the description covers the key decision points: model schema lookup, attachment routing, session/version selection, identifier preservation, and failure handling. It is more than complete, even if overlong.

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

Parameters4/5

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

Schema coverage is high (86%), but the description still adds routing meaning: use reference_files/file_bindings for native attachments, put existing URLs in input, do not mix media URLs with reference_files, and use session_id/base_run_id for continuation/versioning. It also warns against legacy flat parameters and unaccepted fields.

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 opening sentence names a specific verb and resource: 'Create one independent billable Studio task.' It also distinguishes this tool from shortcuts by noting that generate_task requires model while shortcuts may omit it, so an agent can identify the tool's role.

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

Usage Guidelines4/5

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

The description gives detailed routing for attachments (reference_files vs upload_reference) and session usage (session_title, session_id, base_run_id), plus fallbacks when uploads fail. However, it never explicitly states when to choose generate_task over the named shortcut siblings such as generate_image or generate_video; the 'shortcuts may omit model' line only implies the split.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources