Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dailymotion video subtitles

dailymotion_video_subtitles_list
Read-onlyIdempotent

List the available subtitle languages for a Dailymotion video by its video ID to check which caption tracks exist before transcription or translation.

Instructions

List the subtitle tracks (languages) of a Dailymotion video. Requires videoId. Returns a list.

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": {
      "videoId": "<videoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_video_subtitles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
videoIdYesRequired. Dailymotion video id, e.g. `x9hffw2`. A video URL such as https://www.dailymotion.com/video/x9hffw2 is also accepted.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only 'Returns a list', with no mention of what a track entry contains (language code, URL?), what happens when a video has no subtitles, or any pagination behavior.

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?

Three short sentences, front-loaded with the purpose and with no filler. The 'Requires `videoId`' clause slightly duplicates the schema's own 'Required.' marker, which is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with full annotation coverage and 100% schema documentation, the description covers purpose and return type adequately. It is incomplete only in not clarifying its relationship to the transcript sibling or the shape of the returned subtitle entries, which matters given there is no output schema.

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%, so all four parameters, including the required videoId and the context/llm_model/conversation_id bookkeeping fields, are already documented. The description only restates that videoId is required, adding no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource: list the subtitle tracks (languages) of a Dailymotion video. The parenthetical clarifies that tracks are languages, and the Dailymotion scope separates it from the Vimeo captions/transcript siblings. It stops short of explicitly contrasting with dailymotion_video_transcript_get, which also deals with subtitles.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance and no alternatives. It does not say whether to pick this over dailymotion_video_transcript_get when the user wants caption text rather than the track listing, leaving the agent to infer the distinction from tool names alone.

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

Deploy Server

Other Tools