Skip to main content
Glama

Refs

by video.refs
OverviewDiscussionsAdmin

Get your brand kit and films

get_brand

One of your brand imports: the brand kit (the brand's house style across all its films: palette, type, logo and end card, motion and easing, pacing and cut rhythm, camera, transitions, sound and voice, recurring formats, written as rules to follow) plus each film's blueprint summary with its id (brand::) for get_blueprint and get_frames. Private to you. To make a new film in this style, call plan_video(brief, brand: id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAn import id from list_brands, a refs.video/b/… link, or the X handle you imported (e.g. @yourbrand)
limitNoFilms to include; default 20
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It says 'Private to you' and enumerates the returned data, but does not explicitly state read-only/no-side-effect behavior, permission requirements beyond privacy, or failure behavior for invalid ids.

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 description is three sentences, but the first is a long parenthetical catalog of brand-kit dimensions. It is information-dense and mostly front-loaded; trimming would improve scanability, though the detail earns its place.

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?

For a retrieval tool with full schema coverage and no output schema, it explains the returned brand kit and film summaries, the privacy scope, and how to use returned film ids. No critical calling information is missing.

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 the schema already documents id, limit, context, and llm_model. The description adds no meaningful parameter semantics beyond the return id format and downstream usage, so the baseline of 3 is appropriate.

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 specifies the resource (a brand import), the returned bundle (brand kit rules plus film blueprint summaries and film ids), and points to get_blueprint/get_frames. It distinguishes this from plan_video, but does not explicitly contrast with list_brands as the discovery tool.

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 clear context: use the returned film ids with get_blueprint/get_frames, and call plan_video(brief, brand: id) to make a new film in this style. It lacks an explicit when-not-to-use or a direct alternative for listing brands, though the schema notes list_brands for the id.

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

All Refs toolsInspect
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