flayr

Add a frame to the library

create_frame

[writes flayr data · write scope] Copy a flayr frame into the brand library (defaultKey, optional colors/texts), or add uploaded PNG/SVG art (upload_media first; variants of storageIds, the content area is detected from transparency). (Wraps POST /api/v2/frames.)

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": "create_frame"
  }
}

Input Schema

Name	Required	Description
`kind`	No	Default: guessed from the name.
`name`	No
`tags`	No
`texts`	No	Texts some frames print (ribbon/tag label, lower-third title/subtitle).
`rights`	No	Who holds the rights to the art. Optional; a frame without it shows a reminder.
`variants`	No	One per aspect ratio.
`defaultKey`	No	A defaults[].ref without "default:".
`paletteOverride`	No	Colors that win over the brand kit.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, non-destructive, non-idempotent and closed-world, so the safety profile is covered. The description earns credit on top of that by disclosing the two distinct creation modes, the upload_media prerequisite chain, automatic content-area detection from transparency, and the 'rights reminder' post-condition. It does not warn that repeat calls create duplicate frames despite idempotentHint=false.

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?

It is one tight, front-loaded sentence with the scope marker leading, and nothing is wasted. However, the dense nested parentheticals and inline backticked field names make it harder to parse than it needs to be for a two-mode 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 an 8-parameter, nested-object tool with no output schema, the description covers both invocation paths, the required upstream call, and one notable side effect (missing rights shows a reminder). Failure behavior and duplicate-creation semantics are the remaining gaps.

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 75%, so the schema carries most weight, but the description adds real disambiguation by mapping parameters to modes: defaultKey plus colors/texts for the copy path, variants-of-storageIds and auto-detected content area for the upload path. tags and paletteOverride are left to the schema alone.

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 concrete verb-and-resource pair: copy an existing flayr frame into the brand library, or register uploaded PNG/SVG art as a frame. It is clearly distinct from apply_frame/get_frame/list_frames, but it never names or contrasts with the closest sibling, import_frames, so an agent must infer the boundary.

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?

It gives operational context rather than just a purpose: the write scope is flagged, and 'upload_media first' is an explicit prerequisite routing to a sibling tool. It stops short of stating when not to use this tool or naming the alternative (e.g. import_frames) for bulk cases.

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

All flayr 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?