Montik

Use asset

use_asset

Add files from the workspace's library (assetId from list_media or search_media from: folder or workspace) to this project. The project uses the same asset: nothing is stored, transcribed or tagged again, and its tags stay in step. Then place them with add_clip. Files already here are skipped. Like an upload, it isn't an undo step: remove_media takes one out of the project.

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": {
      "assetIds": "<assetIds>"
    },
    "name": "use_asset"
  }
}

Input Schema

Name	Required	Description
`binId`	No	bin to add into (default: library root)
`assetIds`	Yes
`projectId`	No	Project to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the supplied annotations: no re-storage, transcription or tagging, tags stay in sync, already-present files are skipped (idempotent behavior), and notably it is not an undo step so undo will not revert it. Those are exactly the non-obvious traits an agent needs before mutating a project.

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?

Front-loaded with the action and scope, then flows into provenance, placement, and undo semantics with little waste. A couple of clauses are dense ('nothing is stored, transcribed or tagged again, and its tags stay in step'), but each sentence carries distinct information.

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

Completeness4/5

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

For a three-parameter mutation tool with no output schema, the description covers the important behavior: idempotency, undo interaction, and follow-up/removal tools. Gaps are minor — binId's meaning and any indication of what the call reports back are left unaddressed, though annotations cover the safety profile.

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?

Adds real meaning for assetIds by documenting its provenance and acceptable scopes, which the schema's bare string-array type does not convey. It does not explain binId's semantics or the effect of the projectId default beyond what the schema already states, leaving one of three parameters only schema-covered.

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?

States a specific verb and resource ('Add files from the workspace's library ... to this project') and immediately disambiguates from the near-synonym sibling by explaining that it only attaches the asset and that placement happens via add_clip. It also clarifies this is not an upload, which rules out another plausible reading.

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?

Explicitly tells the agent where assetIds come from (list_media or search_media, folder or workspace scope), what to do next (add_clip), and how to reverse it (remove_media). The condition selecting this tool over add_clip is spelled out rather than implied.

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

All Montik tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?