Skip to main content
Glama

Check videos against each place's limits

check_place_limits
Destructive

Checks finished MP4s against Instagram, YouTube, TikTok and other places' published limits—shape, size, frame rate, length, codecs, and caption safe areas—without altering the video.

Instructions

Use it when the user wants a video checked against a place's limits, or burned captions against a phone app's safe area. Measures finished MP4 files against each place's published limits without changing them: shape, size, frame rate, length, file size, codecs, and whether the MP4 is whole and laid out as Instagram and YouTube ask. Give it a folder reframe_video made, its formats.json, or one MP4 with the places in for. With captions, the ASS, SRT or WebVTT file burned into the video, it checks their timing, and an ASS file's text against each 9:16 place's safe area. It writes CHECK.md, which the result shows, and check.json. A failed check is a normal result, with what failed and the limit's source. It does not say whether a video may be posted. For loudness, black, still and silent stretches, use check_video instead. The reframe playbook (makersmcp_playbook) has the whole job. (reframekit 0.1.3, on this machine.)

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": {
      "target": "<target>"
    },
    "name": "check_place_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
forNoThe places to check a lone MP4 against, any of tiktok, reels, shorts, youtube, x, linkedin, feed and square (default: the places of its shape); with a folder, only these.
targetYesWhat to check: a folder reframe_video made, its formats.json, or one MP4, like captioned.mp4.
out_dirNoFolder to save into, absolute or relative to /app. Default: <target-folder>/reframekit-check-<target-name>, where <target-name> is the name of target without its extension and <target-folder> is the folder target is in.
captionsNoThe ASS, SRT or WebVTT file of the captions burned into the video: its timing is checked, and an ASS file's text against each 9:16 place's safe area. caption_video writes captions.ass beside its captioned.mp4.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that it writes CHECK.md and check.json, that a failed check is a normal result carrying what failed and the limit's source, and that it returns a job_id if the wait elapses. The gap is that destructiveHint=true is only partially reconciled: it says it measures 'without changing' the limits and writes into out_dir, but doesn't say whether an existing out_dir is overwritten.

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-loads the when-to-use clause, then scope, then artifacts, then exclusions and pointers — a sensible order with little waste. It is one long run-on paragraph, which slightly hurts scanability but each clause carries information.

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 a five-parameter tool with job polling and file outputs, the description covers what is checked, what is written, how failures surface, and which sibling to use instead, and an output schema exists so return internals need not be spelled out. Minor omission is any statement about overwrite behavior in out_dir given destructiveHint=true.

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 the schema already documents every parameter in detail and the baseline is 3. The description mostly restates target as 'a folder reframe_video made, its formats.json, or one MP4' and captions as the burned-in subtitle file, adding only the useful cross-reference that caption_video writes captions.ass beside its captioned.mp4.

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 ('checked against a place's limits') plus the concrete objects it inspects: shape, size, frame rate, length, file size, codecs, MP4 structure, and burned-caption timing/safe area. It also explicitly separates itself from check_video, so an agent can distinguish it from siblings without opening schemas.

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?

'Use it when the user wants a video checked against a place's limits, or burned captions against a phone app's safe area' gives the selection condition, and 'For loudness, black, still and silent stretches, use check_video instead' names the alternative and the condition that selects it. The playbook pointer adds a second route for the full job.

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