Skip to main content
Glama

Al Jazeera 360

by io.github.ahmedaminsa
OverviewDiscussionsAdmin

get_transcript

Read-only
Get the full text of an episode: the platform's own subtitle file (WebVTT/SRT) when the
episode has one, otherwise a transcript already saved in the video index. Returns the
text with timestamps, plain text, or a ready SRT/VTT file. If neither exists, says so and
lists the subtitle languages that are available. On the team endpoint, saved transcripts
also come with download links (text, SRT, VTT) to the full file.

نص الحلقة الكامل: ملف الترجمة الخاص بالمنصة إن وجد، أو التفريغ المحفوظ في الفهرس.

Args:
    video_id: Video ID
    language: Subtitle language code (default "ar"; falls back to another language if absent)
    format: text (timestamped lines) | plain | srt | vtt
    start_minute: Start of the range, in minutes (default 0)
    end_minute: End of the range (default: end of the episode)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext
languageNoar
video_idYes
end_minuteNo
start_minuteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=true, so the description carries most of the behavioral burden and does add real context: source precedence, the fallback-language rule, the 'if neither exists, list available languages' outcome, and team-endpoint download links. It does not mention pagination or size limits, but for a read-only tool this is a solid disclosure.

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

Conciseness3/5

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

The English portion is front-loaded and efficient, but the Arabic sentence is a near-verbatim restatement of the opening, adding length without new information, and the Args block partially duplicates the schema. Structure is clean but not lean.

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 an output schema present, return-format explanation is not required, and the description covers the source logic, all five parameters, and failure behavior. It is nearly complete; only the absence of any sibling-routing guidance keeps it from full marks.

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 description coverage is 0%, so the description must compensate, and it largely does: every one of the five parameters is documented with meaning and defaults (language default 'ar' with fallback, format options text|plain|srt|vtt, start_minute default 0, end_minute defaulting to episode end). It supplies enum values the schema lacks entirely.

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 names a specific verb+resource ('Get the full text of an episode') and precisely defines the two content sources (platform subtitle file vs. indexed transcript), including the fallback order. An agent can distinguish this from index-searching siblings like search_video_index without opening 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 Guidelines3/5

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

It clearly describes internal behavior (source precedence, range filtering, language fallback) and what happens when nothing exists, but never states when to pick this tool over a sibling such as search_video_index or get_video_analysis. Usage is implied rather than routed.

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

All Al Jazeera 360 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