Skip to main content
Glama

Screens from a recording

screens_from_recording

Takes the screens from a short screen recording (up to a minute) the person uploaded: one screenshot each time the screen rests. They go into the brand kit; suggest_regions then boxes their cards. 2 credits. Runs in the background: returns a task_id for get_task.

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": {
      "brand_id": "<brand_id>",
      "video": "<video>"
    },
    "name": "screens_from_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYesThe recording in studio storage (uploads/...): an MP4, WebM or MOV of up to a minute
brand_idYesA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: a 2-credit cost, an input limit of up to a minute, the extraction rule (one screenshot each time the screen rests), the destination (brand kit), and the async contract (runs in background, returns task_id for get_task). These are exactly the traits an agent needs before committing a paid, non-blocking job.

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?

Dense and front-loaded: purpose first, then destination/chaining, then cost and async contract. The fragment 'suggest_regions then boxes their cards' is slightly cryptic but earns its place by naming the next step.

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 covers the return contract (task_id for get_task), the cost, the duration limit, and the follow-up tool. Nothing material for correct invocation 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%, so the baseline is 3; the description still adds meaning by clarifying the video is a short uploaded recording and that brand_id determines where the extracted screens land ('They go into the brand kit'). It stops short of adding format or naming details beyond the schema.

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?

States a specific verb and resource: extract screens from a screen recording, one screenshot per screen rest. It is concrete enough to distinguish from render/compose siblings, though it never names the closest alternative (add_screens) to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies when to use via 'a short screen recording the person uploaded' and gives the downstream workflow ('They go into the brand kit; suggest_regions then boxes their cards'). However, there is no explicit when-not-to-use or comparison to add_screens, so the agent must infer which ingestion path applies.

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