Montik

Search media

search_media

Read-only

Search the media library by file name, bin, what is in the shot (tags, description, readable text, moments) and spoken words in transcripts. Returns matches with the moments where it happens or is said (t in seconds of the source). Use it to find B-roll ("coffee cup", "outdoor") or a line ("game changer"). from: folder or workspace search those libraries, where words match by their start and bins and favourites don't apply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_media"
  }
}

Input Schema

Name	Required	Description
`from`	No	folder: the folder's media, shared by its projects; workspace: every file in the workspace's library, under the project or folder it lives in (default: this project)
`type`	No
`binId`	No
`limit`	No
`query`	No
`favorite`	No
`projectId`	No	Project to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / from / description

Previous value: -"folder: the folder's media, shared by its projects (default: this project)"New value: +"folder: the folder's media, shared by its projects; workspace: every file in the workspace's library, under the project or folder it lives in (default: this project)"

changedInput schema / properties / from / enum

Previous value: -[
-  "project",
-  "folder"
-]New value: +[
+  "project",
+  "folder",
+  "workspace"
+]

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "folder: the folder's media, shared by its projects (default: this project)",
+  "enum": [
+    "project",
+    "folder"
+  ],
+  "type": "string"
+}

First observedNov 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Adds real value beyond the annotations by describing the return shape (matches with the moments where it happens, timestamped in seconds of the source) and by disclosing matching rules (words match by their start; bins and favourites don't apply under `from`). Annotations already cover safety (readOnly, non-destructive), so this is useful extra context rather than the full burden.

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 first two sentences are dense and front-loaded with the useful information. The trailing 'from: folder or workspace search those libraries, where words match by their start and bins and favourites don't apply' is a run-on that is genuinely hard to parse and undercuts an otherwise tight description.

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

Completeness3/5

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

For a 7-parameter search tool with no output schema, the description usefully explains what a match looks like and how query matching works. It still leaves paging/default-limit behavior, filtering by type/favorite/bin, and the precise `from` semantics unexplained, which is a meaningful gap at this complexity.

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

Parameters3/5

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

With only 29% schema coverage, the description does compensate for `query` by explaining what fields are searched, and it gestures at `from` scoping. But `limit`, `type`, `favorite`, and `binId` are undocumented in both schema and description, and the `from` sentence is too garbled to pin down its exact matching behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the media library') and enumerates the searchable facets: file name, bin, on-screen tags/description/OCR/moments, and transcript speech. That is materially more specific than the title, though it never names a sibling such as list_media to draw the boundary.

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

Usage Guidelines3/5

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

Offers concrete usage examples ('find B-roll', 'find a line') that make the intended query style obvious, and hints that scope changes with the `from` value. It gives no explicit when-not guidance and no comparison to list_media or other retrieval siblings.

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?