Skip to main content
Glama

Search production craft skills

search_skills
Read-only

Find Levea production craft playbooks by keyword or category to locate guidance for editing, color grading, captions, audio, motion graphics, VFX, documentary, podcasts, and social shorts.

Instructions

Search Levea production craft skills (SKILL.md playbooks across editing, color grading, captions, audio mixing, motion graphics, VFX, documentary, podcast, and social shorts) by keyword or category.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax skills to return (default 20).
queryNoSearch keyword (e.g. "color", "caption", "podcast", "montage", "motion").
categoryNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description usefully adds that the indexed content is SKILL.md playbooks spanning editing, color, captions, audio, motion, VFX, documentary, podcast and shorts. It does not disclose what a result looks like or how results feed subsequent loading, which is the behavior an agent most needs here.

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?

A single front-loaded sentence with the action and resource stated first; the parenthetical domain list is long but genuinely clarifies corpus scope. No filler or repetition.

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 read-only, three-parameter search with no output schema, the agent still lacks the crucial link between search results and load_skill — whether results contain skill identifiers to fetch or full content. That omission leaves the workflow incomplete even though the tool itself is simple.

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%, so query, category and limit are already documented individually. The description contributes only the framing that keyword and category are alternative discovery dimensions, which is marginal added meaning over the schema.

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 states a specific verb (search) plus the resource (Levea production craft skills / SKILL.md playbooks) and enumerates the domains covered, so an agent knows exactly what corpus is being queried. It does not explicitly differentiate itself from the sibling load_skill tool, which is the natural next step after a search, so it stops short of a 5.

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?

The phrase 'by keyword or category' implies the two discovery modes, but there is no explicit statement of when to reach for this tool versus load_skill or search_tools, nor any when-not guidance. Usage is inferable but left to the agent.

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