Skip to main content
Glama

Find matching library examples

find_matching_examples

Match a brief against hundreds of render-ready examples to receive ranked candidates with thumbnails and a decision: adapt an existing example or assemble from templates.

Instructions

Match a brief against the ENTIRE published examples library (hundreds of professionally designed, render-ready projects) and return ranked candidates with thumbnails/previews plus a decision: "adapt-example" (strong match — call start_from_example), "adapt-or-assemble", or "assemble-similar" (compose from the returned design-template/canvas-preset/shape modules). Use this before authoring any project JSON by hand; matching runs over full metadata with category synonyms, so it finds examples the plain search_creative_library query cannot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRestrict to video examples, still-image examples, or both.any
briefYesWhat to create, for whom, and the goal — same brief you would give plan_creative_video.
limitNo
durationNoTarget video duration in seconds (soft signal).
aspectRatioNo
excludeSlugsNoRecently used example slugs to exclude (anti-repetition).
includePartsNoInclude design-template/canvas-preset/shape modules for assembly. Default: automatic (included unless a strong example match exists).
variationModeNofresh (default) rotates which comparable top candidate leads, so repeated identical briefs vary; "consistent" keeps ranking deterministic.fresh
variationSeedNoOptional reproducible seed for the rotation; omit for a new pick per request.
excludePremiumNoSet true on free-plan accounts to skip premium examples (their content is plan-gated).
Behavior4/5

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

With no annotations, the description bears full burden. It discloses that matching runs over full metadata with category synonyms, the library size (hundreds), and the output includes a decision. It does not mention any destructive implications or authentication needs, but the tool appears to be a read-only search operation. Some detail on return value structure could improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first covers purpose and output, the second provides usage guidance and comparison. It is front-loaded, concise, and every sentence adds value without redundancy.

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?

The description covers main purpose and usage context but lacks details on the exact output structure (e.g., format of ranked candidates, fields in thumbnails/previews). Without an output schema, more information about the returned data would improve completeness for a tool with 10 parameters and no output schema.

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 80% (8 of 10 parameters have descriptions). The tool description does not add extra meaning beyond what the schema already provides for parameters. Baseline is 3 due to high schema coverage, and the description does not elevate it.

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?

The description clearly states the verb 'match', the resource 'ENTIRE published examples library', and the specific output of ranked candidates with thumbnails/previews plus a decision. It distinguishes from the sibling 'search_creative_library' by noting that this tool runs over full metadata with category synonyms.

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

Usage Guidelines4/5

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

The description explicitly instructs to use this tool before authoring any project JSON by hand and explains that it finds examples beyond plain search. It also links the decision values to subsequent actions (start_from_example or compose from modules). However, it does not provide explicit when-not-to-use or list alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zvid-io/zvid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server