MCP tools reference

The Nodaro MCP tools are the actions an AI assistant can take in your Nodaro account once it is connected to the Nodaro MCP server. There are about 200 of them, grouped here by task: generate media, edit it, manage assets, build and run workflows, and direct complete productions. Each page lists the exact tool names, the permission each tool needs, its main parameters, what it returns and what it costs.

The tool groups

Permissions

Each tool needs one or more OAuth permissions (scopes), which you grant on the consent screen when you connect. A tool whose permissions were not granted is left out of the tool list entirely. The assistant never sees it, so it cannot call it and fail.

These tools need no permission and are always visible, on the editions that have them: ping, list_models, start_film_director, start_video_director, start_workflow_editor, get_node_skill, get_picker_catalog, list_shot_shapes, get_shot_shape, list_brand_presets, get_recipe, get_studio_production_skill, get_recast_authoring_skill, validate_recast_script, build_ugc_creator, build_ugc_clips, build_ugc_cards, ugc_split_speech and ugc_finish_clips.

The tools that need two permissions appear only when both were granted. A connection with only one of the pair sees none of those tools.

How a job reports its result

Most generation tools start a job and answer at once with a line such as image collage started (id 7f3c…). The job runs on Nodaro, and its result is always saved to your library as well.

• In clients that display MCP Apps, such as Claude on the web, the tool shows a card. The card shows live progress and then the finished result. Image, video and audio tools have their own cards. Every other job tool shares one card that detects its output: a video, image or audio player, a text with a Copy button for scripts, lyrics, transcripts and alignment data, or the stacked outputs of a component.
• In other clients, the assistant checks the job with get_job every 5 to 10 seconds, or blocks for up to 45 seconds per call with wait_for_job. An image usually finishes within a minute. A video usually takes 2 to 10 minutes.
• Workflow and app runs return a run id instead of a job id. Check it with get_app_run.

Clients that support the MCP tasks API also receive progress through it. When a job waits for human review on a deployment that reviews results, the task shows the status input_required. That decision belongs to the reviewer: do not re-run the job.

The mcp project

The workflow tools work inside one project named mcp. Nodaro creates it the first time an assistant needs it, and the dashboard lists its workflows under MCP Workflows. From that tab you can open, move or delete them like any other workflow.

To let an assistant work on a workflow from another project, export it with export_workflow and import the bundle with import_workflow. The copy lands in the mcp project, and your original stays untouched.

How to read a tool entry

Every tool on these pages has the same layout:

• The heading is the exact tool name, for example generate_image. Assistants call tools by these names.
• The first lines say what the tool does, the permission it needs, what it costs, and whether it exists only on Nodaro Cloud.
• The parameter table lists the main parameters with their type. Required parameters are marked Required. Defaults and limits are in the notes.
• Returns says what comes back: most often a job id, sometimes a result such as a plan or a list.

The tool's own description, which the assistant reads when it connects, is the final word on parameters and limits. A price in a tool description can differ from what a run is charged. list_models returns the current prices of the models. A node's Run button shows the price of its run.

Conventions shared by many tools

• Media by URL or by id. Tools that take media accept a public https URL, such as image_url, or a Nodaro id, such as image_asset_id. An id can be the job that made the media or an upload.
• Models by id. A model parameter takes a model id from list_models, which also returns each model's aspect ratios, resolutions, durations and prices.
• Presets. generate_image, generate_video, generate_music, generate_speech and text_to_audio accept presetId from list_node_presets. Fields you pass yourself override the preset.
• Retry tokens. run_workflow, run_app, run_component and several production tools accept client_request_id: 8 to 128 characters of letters, digits and _ - . :. Reuse the same value when you retry after a timeout, and Nodaro does not start or charge the work twice.
• Quotes before spending. Some tools can price work without starting it, for example the studio tools with dry_run: true; start_recast, cast_swap, run_trend and full_quality without confirm; and estimate_use_case for the podcast tools.

Tools only on Nodaro Cloud

These tools exist only on Nodaro Cloud: check_balance, credit_transactions, train_character, plan_edit, switch_cameras, speaker_view, voice_changer_pro, voice_changer_pro_analyze, voice_changer_pro_export, create_explainer, create_launch_video, start_film_director, pro_3d_render, cast_swap, the trend tools, the workspace tools, the recast tools, the studio production tools, the pipeline tools and the UGC tools. So are estimate_full_quality and full_quality. The workspace tools also need organizations switched on, and pro_3d_render appears only while its render engine is available.