Skip to main content
Glama
Sign In

agent-media-toolkit

by io.github.krakonjac300-pixel
OverviewDiscussionsAdmin

edit_clip

Cut a time range into a finished 9:16 captioned short. Premium (via x402).

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": {
      "source_url": "<source_url>",
      "start_s": "<start_s>",
      "end_s": "<end_s>"
    },
    "name": "edit_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_sYes
styleNobold-captions
start_sYes
source_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions creating a 'finished' short but does not disclose if the source is modified, require authentication, or have rate limits. The 'Premium' hint is vague.

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?

The description is very concise with two sentences. Key action is front-loaded. However, it is overly brief given the tool's complexity, leaving critical details missing.

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

Completeness1/5

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

Given 4 parameters, no schema descriptions, no output schema, and no annotations, the description is far from complete. It does not explain input requirements, output format, or edge cases, making it insufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description should explain parameters but does not. It references a 'time range' but does not map to start_s and end_s, nor explain source_url or style. Parameters remain obscure.

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 description succinctly states the tool creates a finished 9:16 captioned short from a time range. The verb 'Cut' and resource 'clip' are specific, and the mention of '9:16 captioned short' distinguishes it from sibling tools like 'extract' or 'repurpose'.

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?

The description does not provide guidance on when to use this tool versus alternatives. It only indicates it is premium via x402, but no explicit when-to-use, prerequisites, or exclusions.

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

All agent-media-toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources