Skip to main content
Glama

motion.search

Read-onlyIdempotent

Search for similar motion patterns by query or sample pattern, filter by type, duration, trigger, or animation library, and generate CSS/JS implementation code in multiple formats including Tailwind, GSAP, and Framer Motion.

Instructions

モーションパターンを類似検索、または実装コードを生成します。action: search(デフォルト)で検索、action: generateでCSS/JS実装コードを生成します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoアクション: search(デフォルト)= モーション検索、generate = 実装コード生成search
queryNo検索クエリ(自然言語、1-500文字)。action: searchで使用。
samplePatternNoサンプルパターンで類似検索。action: searchで使用。
filtersNo検索フィルター。action: searchで使用。
limitNo結果制限(1-50、デフォルト: 10)。action: searchで使用。
minSimilarityNo最小類似度しきい値(0-1、デフォルト: 0.5)。action: searchで使用。
include_js_animationsNoJSアニメーションパターンを検索結果に含める(デフォルト: true)。action: searchで使用。
js_animation_filtersNoJSアニメーション検索フィルター。action: searchで使用。
include_webgl_animationsNoWebGLアニメーションパターンを検索結果に含める(デフォルト: true)。action: searchで使用。
webgl_animation_filtersNoWebGLアニメーション検索フィルター。action: searchで使用。
include_implementationNo検索結果に実装コード(@keyframes, animation, tailwindクラス)を含める(デフォルト: false)。action: searchで使用。
patternNoモーションパターン定義。action: generateで必須。
formatNo出力フォーマット(デフォルト: css)。action: generateで使用。css
optionsNo生成オプション。action: generateで使用。
profile_idNo嗜好プロファイルID(検索結果のリランキングに使用) / Preference profile ID (used for search result reranking)
Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, which the description does not contradict. The description adds behavioral context by noting that 'generate' produces CSS/JS code (a read-only operation). No hidden side effects are mentioned, and the description aligns well with annotations.

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 extremely concise—two sentences—with no redundant information. It front-loads the core purpose and action distinction, making it easy to parse.

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?

While the schema fully details parameters, the description omits what the tool returns (e.g., search results or generated code format). For a complex tool with no output schema, mentioning the return type would improve completeness. The description covers the essential split but lacks output context.

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 the description does not need to detail parameters. However, it adds value by summarizing the two modes (search/generate) and their default action, helping agents quickly grasp the tool's operation beyond individual parameter descriptions.

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 tool's two main functions: searching for similar motion patterns and generating implementation code. It explicitly maps actions to functions ('action: search' for search, 'action: generate' for code generation), distinguishing it from sibling tools like motion.detect.

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 provides clear guidance on when to use each action (search vs. generate), but does not explicitly contrast this tool with alternatives like motion.detect or other search tools. The context is sufficient for the agent to decide basic usage, but lacks exclusionary advice.

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/TKMD/ReftrixMCP'

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