Subframe Motion

Get Motion Example

get_motion_example

Read-onlyIdempotent

Get one Subframe Motion Library example: its complete React source; how it looks and moves; adapt notes naming the code that drives the motion and what to change; the npm packages to install (none means React only); the images its code loads from /motion/assets/ with download URLs (serve them there or change the paths); reduced-motion behavior and limitations; its licence and upstream credit; related examples; the guidance topics worth reading; and a preview image. Use a slug from search_motion_examples or from a www.subframe.com/motion/ URL. This writes no files: adapt the code to the project, keep its licence header, and test it there. The code targets React 19; with React 18 server rendering, move its inline CSS into a stylesheet, since React 18 escapes the CSS's quotes and > characters.

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": {
      "slug": "<slug>"
    },
    "name": "get_motion_example"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The example's slug, e.g. 'slipstream'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds real operational facts they cannot: "This writes no files," the requirement to keep the licence header, and the React 19 vs React 18 SSR caveat about moving inline <style> CSS to a stylesheet because React 18 escapes quotes and > characters. That last detail is a concrete failure mode an agent would otherwise hit blind.

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?

The operative instruction is front-loaded and no sentence is filler, but the second sentence is an extremely long semicolon-stitched list of deliverables that is hard to scan; splitting it into clauses or bullets would improve retrieval without losing content.

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?

With no output schema, the description carries the full burden of describing the return payload and does so field by field, plus asset handling (/motion/assets/ paths and download URLs), allows no-file-writing, and compatibility caveats. Nothing an agent needs before calling and then consuming the result is missing.

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% (the slug property documents itself with the 'slipstream' example), so the baseline is 3. The description beats that by giving the slug's provenance — derive it from search_motion_examples or strip it out of a subframe.com/motion/<slug> URL — which the schema does not say.

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 definition opens with a specific verb and resource ("Get one Subframe Motion Library example") and then enumerates exactly what the response contains — React source, adapt notes, npm packages, assets, reduced-motion behavior, licence, related examples, guidance topics, preview image. That enumeration makes it unmistakable against the sibling search and guidance tools.

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?

It names the substitute tool explicitly: "Use a slug from search_motion_examples or from a www.subframe.com/motion/<slug> URL," giving both the accepted input source and the URL parsing rule. It also tells the agent what to do with the result (adapt the code to the project, keep the licence header, test it there) rather than fetching blindly.

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

All Subframe Motion 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.

Resources

Need Help?