Skip to main content
Glama

studio_formats

Read-onlyIdempotent

List everything Studio can generate: wall-of-text posts, TikTok slideshows, AI UGC talking heads (selfie, street interview, car yapper, podcast), explainers (a presenter teaching one idea, cut with animated graphics on the spoken words), animated stories, hook + demo videos, voiceovers, images, video clips and consistent AI influencers (avatars). Every format has a credit price per duration (formats with "qualities" also have a Premium price per duration, made with a more realistic model), the inputs it needs (a demo video, a product image or an avatar from the media library) and what it outputs. Also returns the hook formulas that can be passed as "hook" to studio_generate, and the organization's saved avatars. Call this before studio_generate, tell the user the price in credits, and get their confirmation before generating.

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

Input Schema

NameRequiredDescriptionDefault
reasoningNoOptional short reason for listing the formats

Output Schema

NameRequiredDescriptionDefault
hooksYes
avatarsYes
formatsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit for going beyond that by disclosing the shape of the payload — per-duration credit prices, the existence of a Premium tier for formats with 'qualities', required inputs per format (demo video, product image, avatar), outputs, hook formulas usable as 'hook', and org avatars. It does not mention result size or any paging/caching behavior, which is the main residual gap.

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 front-loaded with the core purpose and the operational instruction sits at the end where it will be read before acting. The long parenthetical enumeration of formats ('selfie, street interview, car yapper, podcast') and the nested explanation of explainers is more verbose than needed for tool selection, though it does help the agent describe options to a user.

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 zero-required-parameter discovery tool with an output schema, this covers everything an agent needs: what it returns, that prices are quoted per duration with a Premium variant, what inputs each format requires, and the confirmation step before generating. Return-value details are already in the output schema, so no further detail is owed.

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?

There is a single optional 'reasoning' parameter that is fully documented in the schema at 100% coverage, so no further explanation is required in the description. The description correctly adds nothing here; a 4 reflects that the schema carries this burden entirely and the description does not misdescribe the parameter.

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 opening sentence names a specific verb and resource ('List everything Studio can generate') and then enumerates the format families, so an agent immediately knows this is the catalog/discovery tool rather than a generation tool. It also states the secondary payloads (hook formulas, saved avatars), which separates it cleanly from siblings like studio_generate and hooks_generate.

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?

The final sentence gives explicit sequencing and a mandatory workflow step: call this before studio_generate, quote the credit price to the user, and obtain confirmation before generating. That is a concrete when-to-use plus a prerequisite the agent would otherwise miss; the only thing absent is an explicit 'do not call when...' exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources