Skip to main content
Glama

Put the real app on screen

place_screen

Put the brand's real screenshot on the phone or tablet screen in a lifestyle still or clip. Generate the still with green_screen: true (its screen comes out plain green), then place_screen on the still, or on the clip animate_image makes from it: the screen is found and followed in every frame and the app stays sharp, with hands in front of the screen kept in front. Returns checks: a phone that rocks or shakes in the clip (animate again), app text too small to read, frames where the screen was lost. 5 credits. A still comes back straight away; a clip returns a task_id at once, so follow with get_task.

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

Input Schema

NameRequiredDescriptionDefault
imageNoOr a still: stored path (assets/..., uploads/...) or public https
videoNoOr a clip: stored path or public https MP4
cornersNoStills only: the screen's corners as fractions of the image (top-left, top-right, bottom-right, bottom-left), when it isn't green
asset_idNoThe screenshot to show, from the brand kit. With brand_id and no asset_id or screenshot, the kit's first screenshot.
brand_idNoA 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.
job_tokenNoA finished image or video job_token (generate_assets with green_screen, or animate_image of that still)
screenshotNoOr a stored or public https screenshot
status_barNoPhone screens: true when the screenshot starts at the app's own header with no phone status bar (captured in a browser); a status bar in the header's colour goes above it, so the camera island doesn't cover the header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare write/open-world/non-idempotent, so the description carries the real burden and does so: per-frame screen tracking, occlusion handling for hands in front of the screen, cost of 5 credits, immediate return for stills vs. task_id for clips, and a named list of returned checks (rocking phone, unreadable text, lost frames). That is materially more than the annotations convey.

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?

Front-loaded with the core action and the input chain, then costs and return behavior. Efficient overall, but the long compound sentence about tracking and hands is dense and could be split for faster scanning.

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?

All 8 parameters are optional, there is no output schema, and the description covers what an agent needs to call it correctly: which upstream tool to run first, sync vs. async return, follow-up with get_task, cost, and what the checks mean. Nothing essential 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 coverage is 100%, so parameter documentation is already handled. The description adds useful framing for the green_screen/job_token input path but says nothing about corners (the manual fallback for non-green stills), status_bar, or the asset_id/brand_id defaults, so it does not meaningfully exceed the schema baseline.

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?

States a specific verb and resource — 'Put the brand's real screenshot on the phone or tablet screen in a lifestyle still or clip' — and names the medium (still vs. clip) and the input chain (green_screen still, animate_image clip). An agent can distinguish this from add_screens or make_screen_scene purely from this sentence.

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?

Gives an explicit prerequisite and sequence: generate the still with green_screen: true so the screen comes out plain green, then place_screen on that still or on the clip animate_image makes from it. It also tells the agent to follow with get_task for clips. No when-not or explicit alternative tool is named, which keeps it short of a 5.

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