Skip to main content
Glama

Make a watch link

share_video

Prepare the video (or just the part between start and end) and return a short gimmeclip.com/w/… link anyone can open and play, kept for 30 days. Counts against the caller's daily limit (40 per IP, 200 with an API key) unless the same clip was shared before. If it returns a job_id, call share_video again with that job_id to keep waiting.

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

Input Schema

NameRequiredDescriptionDefault
endNoOptional: end of the part to keep, in seconds (after start).
urlNoLink to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo).
itemNoWhich video of a multi-video post (1-based); see get_video_info.
startNoOptional: start of the part to keep, in seconds.
job_idNoOnly to resume: job_id from an earlier share_video call that was still preparing.
qualityNoResolution cap (the smaller side, so vertical videos count the same).720

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates remote state and reaches outside the system. The description adds genuinely useful behavior beyond that: 30-day link lifetime, per-IP/API-key quotas of 40 and 200, no charge for deduplicated clips, and a job_id polling protocol. That added context is why this scores above the annotated baseline rather than at it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: the core action and artifact first, then the quota caveat, then the resume path. Every clause carries operational information and nothing is repeated from the schema.

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?

With no output schema, the description correctly takes on the return-value burden, explaining the short link and the job_id case. What is missing is failure behavior — what happens on an unsupported or private URL, and what a quota-exceeded response looks like — which matters for a six-parameter open-world tool.

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 goes modestly beyond by framing start/end as defining the exact clip that is shared and deduplicated, and by characterizing job_id purely as a resume token. It does not, however, add format or unit detail beyond what the schema already documents.

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?

The description states a specific verb+resource: prepare a video (or a start/end slice of one) and return a short gimmeclip.com/w/… playback link. That is clearly distinguishable from download_video or edit_video by the artifact produced, though it never names a sibling to contrast with explicitly.

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?

Usage context is implied rather than spelled out: the url must be a public post, item selects among multi-video posts, and job_id is only for resuming an unfinished call. There is no statement of when to prefer this over downloading or editing, and no explicit exclusion, so the agent must infer the routing.

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