Skip to main content
Glama

export

Encodes finished videos as H.264/AAC in the chosen social platform’s shape and enforces its file-size limit; use max_mb to override the default cap.

Instructions

Ready to post: the platform's shape, H.264 + AAC, file size under the limit. platform: shorts | reels | tiktok | facebook (10 MB) | youtube | x | square. max_mb overrides the size limit.

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

Input Schema

NameRequiredDescriptionDefault
videoYes
max_mbNo
platformNoshorts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare it is a non-read-only but non-destructive, closed-world operation. The description adds genuinely useful behavior beyond that: output codec/container behavior (H.264 + AAC), the hard size constraint, and the fact that max_mb overrides the preset limit. It does not say where the export lands, whether the source is modified, or what a failure at the size limit looks like.

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?

Two dense sentences with no filler and the key constraint stated up front. The telegraphic, fragmentary style ('Ready to post: the platform's shape') costs some readability and the platform list lacks an explicit lead-in verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no output schema, the description covers the platform/size axis well but leaves the return value, source-file fate, and error behavior unaddressed. Adequate to call it correctly, incomplete to predict what happens.

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 0% with no enums, so the description carries the full burden -- and it does the most important part by enumerating all seven platform values and pinning facebook to 10 MB. It also explains max_mb's override relationship to the preset limit. The video parameter itself is left undescribed, which is the only notable gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the outcome (a post-ready file with platform shape, H.264 + AAC, size under limit) but never states a verb or resource explicitly -- 'export' is only implied by the name, not by the text. An agent can infer this produces a platform-formatted video, but it has to infer it.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no reference to alternatives such as estimate or build_video. 'Ready to post' hints at a final stage but does not say whether this should be run after editing, whether it re-encodes, or whether it replaces the source.

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