Skip to main content
Glama

Search canonical editor tools

search_tools
Read-only

Search video editing actions and preset catalogs for captions, VFX, transitions, color presets, titles, fonts, and blend modes by keyword or filter to find matching assets and editorial guidance.

Instructions

Search all 189+ canonical video editing actions, 13 read/inspection tools, AND canonical preset catalogs (280+ caption templates, 328+ GPU VFX effects, 170+ transitions, 50+ color grade LUTs, 59 title cards, fonts, blend modes) by keyword, category, or catalog filter. Returns matching actions, catalog presets, and the 5-phase NLE editorialPlaybook.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (default 50).
queryNoOptional search keyword (e.g. "karaoke", "hormozi", "lens_blur", "whip_pan", "teal_orange", "chromakey").
catalogNoOptional catalog filter: "captions" (280+ caption templates), "vfx" (328+ GPU effects), "transitions" (170+ transitions), "color_presets" (LUTs), "title_cards", "fonts", "blend_modes", "properties", "animatable", "actions", or "all" (default).
categoryNoOptional domain/category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds genuinely new behavioral information by disclosing the return composition — matching actions, catalog presets, and the 5-phase NLE editorialPlaybook — which is the single most important thing an agent needs to know before calling. Since no output schema exists, this is where that contract has to live, and it does. It omits any note on pagination, ranking, or what happens with an empty query (full dump vs. nothing).

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 verb and resource, and the scope is established before the enumeration. The parenthetical count-stuffing ("280+ caption templates, 328+ GPU VFX effects, 170+ transitions, 50+ color grade LUTs, 59 title cards") duplicates the enum and inflates the sentence, but the total length is still reasonable for a catalog-discovery tool.

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 zero-required-parameter search tool with no output schema, the definition covers the corpus, the filter axes, and the shape of the response, which is enough for correct invocation. The remaining gap is behavioral edge cases — default result volume, how limit interacts with catalog filtering, and whether an empty query returns everything — none of which is stated anywhere.

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?

Schema description coverage is 100% and the enum already spells out each catalog value with its counts, so the description adds little semantic meaning beyond restating those same catalogs and a handful of keywords already present in the schema's query examples. Baseline 3 is appropriate: the schema is doing the parameter documentation work here.

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?

The description opens with a specific verb and resource ("Search all 189+ canonical video editing actions, 13 read/inspection tools, AND canonical preset catalogs") and enumerates the catalog families, so an agent knows exactly what corpus is being searched. It stops short of naming a sibling (e.g., search_skills, execute_action) to contrast against, so the reader must infer the boundary from the sibling list alone.

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?

Usage is only implied: the keyword examples ("karaoke", "whip_pan", "teal_orange") and the catalog enum make clear this is a discovery/lookup entry point, and the mention of returning the editorialPlaybook hints at its role as a starting step. There is no explicit statement of when to prefer this over search_skills, get_action_schema, or execute_action, nor any note about when a catalog filter is preferred over a free-text query.

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