Skip to main content
Glama
Sign In

x-toolkit

by app.x-toolkit
OverviewDiscussionsAdmin

Get an X video transcript

get_x_video_transcript
Read-onlyIdempotent

Returns the transcript of the video in an X (Twitter) post: X's own captions when they exist, or a transcript x-toolkit made earlier. If there is none yet, it says so; call transcribe_x_video to make one.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA post link like https://x.com/name/status/123…, or the numeric post ID.
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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the dual-source resolution order (X captions first, then a cached x-toolkit transcript) and the empty-result case. However it says nothing about coverage limits, language handling, or what happens for non-video posts, which are the plausible failure modes for an open-world read.

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?

Two short sentences, front-loaded with the resource and the source resolution, then the fallback action. Every clause carries information; nothing is redundant with the title.

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?

For a two-parameter read tool with no output schema, the description covers what is returned, where it comes from, and what to do when it is empty. The only real gap is that it does not describe the content or structure of the returned transcript, though the format parameter in the schema partly compensates.

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

Parameters3/5

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

Schema description coverage is 100%, with both the url formats and every format enum value documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ("Returns the transcript of the video in an X (Twitter) post") and immediately clarifies the two possible sources of that transcript. An agent can distinguish it from read_x_post and transcribe_x_video without inspecting any 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?

Gives explicit fallback routing: if no transcript exists, "call transcribe_x_video to make one." That covers the main decision point. It does not address when an agent should prefer this over read_x_post for the same URL, so it stops just short of full alternatives coverage.

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