Skip to main content
Glama
Sign In

Tellscreen

by io.github.theguysaccount
OverviewDiscussionsAdmin

Turn a video link into a change list

convert_video_link

Use when the user gives you a link to a video (a screen recording, product walkthrough, bug repro or design review: an .mp4/.mov/.webm URL, or a public Google Drive or Dropbox link) and you need to know what it shows or asks for, because you cannot watch video. Tellscreen transcribes it, looks at the screen at the moment each thing was said, and returns Markdown: a summary, every change asked for with the words said, where on screen, how to check it is done and a screenshot link of that moment, then the timed transcript. Waits up to 50 seconds; if it is still working you get a job id for get_change_list. Loom and YouTube pages cannot be fetched: ask the user for the downloaded file instead and use convert_local_video.

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": {
      "url": "<url>"
    },
    "name": "convert_video_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirect link to the video file, or a public Google Drive / Dropbox link.
titleNoOptional title for the video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the substantive behavior: it transcribes, samples the screen at each spoken moment, returns Markdown with summary, change list, verification steps and screenshot links, and blocks up to 50 seconds before handing back a job id. That timeout/async fallback is exactly the kind of trait annotations cannot express.

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?

A single dense paragraph, but it is front-loaded with the trigger condition and then the return shape, so an agent can stop reading early. Slightly long and clause-heavy, though nearly every clause carries operational information.

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?

There is no output schema, and the description compensates fully by describing the Markdown return structure and the async job-id path. Combined with the URL constraints and the 50-second wait, an agent has everything needed to call it and interpret the result.

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, but the description adds real meaning: it enumerates accepted URL forms (.mp4/.mov/.webm, public Google Drive or Dropbox) and rules out Loom/YouTube links, which the schema does not say. The optional title parameter is not discussed, a minor gap.

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 ('Turn a video link into a change list') and immediately scopes it to screen recordings, walkthroughs, bug repros and design reviews. It is clearly distinguishable from convert_local_video (local files) and get_change_list (job polling), which are named explicitly.

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?

Gives an explicit trigger ('Use when the user gives you a link to a video... because you cannot watch video') and explicit exclusions with the correct alternative: Loom and YouTube pages cannot be fetched, so ask for the downloaded file and use convert_local_video. Both when-to-use and when-not-to-use are covered.

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

All Tellscreen 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