Vidova

Search the Library

search_library

Read-onlyIdempotent

Search the user's Library: every file they have uploaded, in any project or on the Library page, newest first. Use it when the user names or asks for their own footage, photos or sounds that are not in the open project; search_assets lists only the project's media. Files attached to their message are the footage they mean: never search the Library to fill a film. query matches words in file names. To find visual or audible content, use search_video_moments; use read_video_intelligence with a Library id to check indexing progress. Each result has the file's Library id, name, kind, durationSeconds, width and height, createdAt (when it was uploaded) and usedIn (how many projects use it); state is set while a file is not ready. Look at a file before adding it with read_asset and its Library id: a picture, a contact sheet or frames of a range of a video, part of a frame, a sound's waveform and spectrum over a range, or a 3D model from four sides. Add files to the open project with add_from_library and their ids. Works with or without an open 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": {
      "query": "<query>",
      "kind": "<kind>",
      "limit": "<limit>",
      "cursor": "<cursor>"
    },
    "name": "search_library"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Only files of this kind. null lists every kind.
`limit`	Yes	Most files to return, 1 to 100. null means 20.
`query`	Yes	Words in the file name, for example beach or interview. null or empty lists every file.
`cursor`	Yes	Where the next page starts: the cursor the page before ended with, with the same query and kind. null starts at the newest file.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Where the next page starts: the cursor the page before ended with, with the same query and kind. null starts at the newest file."
+}

changedInput schema / required

Previous value: -[
-  "query",
-  "kind",
-  "limit"
-]New value: +[
+  "query",
+  "kind",
+  "limit",
+  "cursor"
+]

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavior: results are newest-first, pagination is cursor-based, a 'state' field appears while a file is not ready, and the full result shape is enumerated. It also routes the agent to read_asset before adding and to add_from_library for insertion.

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 purpose and the primary disambiguation, then result shape, then next-step workflow. Dense but nearly every sentence carries routing or behavioral information; the read_asset/add_from_library workflow sentences are useful but push it toward being overstuffed for a search tool.

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?

No output schema exists, and the description compensates by enumerating every returned field (id, name, kind, durationSeconds, width, height, createdAt, usedIn, state). Combined with ordering, pagination, and follow-up tool guidance, an agent has everything needed to call and chain it correctly.

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 100%, so baseline is 3, but the description adds meaning the schema does not: 'query matches words in file names' clarifies that content is not searched, which is the key semantic distinction from search_video_moments. It does not add detail on limit or cursor beyond the schema, so not a 5.

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 ('Search the user's Library: every file they have uploaded, in any project or on the Library page') and immediately scopes it against siblings: search_assets lists only project media, search_video_moments finds visual/audible content. An agent can distinguish it from the many search_* siblings without opening a schema.

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?

Explicit when-to-use ('when the user names or asks for their own footage, photos or sounds that are not in the open project'), explicit when-not ('never search the Library to fill a film'), and named alternatives for each adjacent case (search_assets, search_video_moments, read_video_intelligence). It also states it works with or without an open project.

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

All Vidova 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.