Skip to main content
Glama
Sign In

x-toolkit

by app.x-toolkit
OverviewDiscussionsAdmin

Transcribe an X video

transcribe_x_video

Transcribes the video in an X post that has no captions, one part (about 108 seconds of audio) per call. Start with part 0. Each call says whether to call again with the next part; the last one returns the transcript. The transcript is saved, so get_x_video_transcript works for it afterwards. Videos up to 15 minutes. Only text is stored, never video or audio.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA post link like https://x.com/name/status/123…, or the numeric post ID.
partNoWhich part to transcribe. 0 to start.
formatNomd (default) has a header and timestamps per paragraph; txt is plain paragraphs; srt and vtt are subtitles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only say it is not read-only, is open-world, non-idempotent and non-destructive, while the description explains the paged protocol (~108s per call), the continuation signal returned by each call, the 15-minute cap, that the transcript is persisted and retrievable via get_x_video_transcript, and that only text is stored. This is exactly the operational context an agent cannot infer from structured fields.

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?

Five short sentences, front-loaded with the core action and the pagination instruction immediately after. Every sentence carries information; a small amount of tightening is possible around the storage note, but nothing is filler.

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 by explaining what each call returns (a continue/stop signal) and what the final call yields (the transcript). Combined with the size limit, pagination model, and persistence note, an agent has everything needed to drive the tool to completion.

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 semantics for 'part' that the schema does not convey: each call covers about 108 seconds, you start at part 0, and the response tells you whether another part is needed. The 'format' parameter is left entirely to the schema.

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 (transcribe the video in an X post) plus a scoping constraint that separates it from siblings: only for posts with no captions. It also names get_x_video_transcript as the follow-up retrieval path, so an agent can distinguish the two without opening a schema.

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

Usage Guidelines4/5

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

The 'has no captions' condition effectively tells the agent when this tool applies, and it explicitly points to get_x_video_transcript for later retrieval. It lacks an explicit negative case (e.g., what to do for posts that already have captions), so it stops short of full when/when-not guidance.

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

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