Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List related Dailymotion videos

dailymotion_video_related_list
Read-onlyIdempotent

Fetch related videos for a Dailymotion video ID to find similar content and power recommendations. Returns a paginated list for browsing related items.

Instructions

List the videos Dailymotion relates to a video. Requires videoId. Returns a list (use page when paginated).

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_related_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
limitNoRows per page (1-100). Default: 30. A page costs the same at any size. A list never reaches past 1000 rows, so a page size of 100 reaches at most page 10.
sourceNo`site` (default) is the site's related list: 30 to 90 videos, redrawn each call, page 1 only. `api` is a shorter fixed list of 17 to 18 videos that pages.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description adds a pagination hint, but it is vague and does not mention the important split between the non-paged 'site' list and the paged 'api' list that the schema documents. Nothing about result volatility (list redrawn each call) appears in the description.

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 action and resource, with no filler. The trailing parenthetical "(use page when paginated)" is slightly vague and partly redundant with the schema, keeping it from a 5.

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?

With 7 parameters, an enum-bearing source option and no output schema, the description is thin: it never explains that the default 'site' source returns 30-90 videos without real pagination while 'api' returns a fixed 17-18 item paged list. An agent could call it correctly using the schema alone, but the description does not stand on its own for this complexity.

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 the baseline is 3. The description restates that videoId is required and gestures at the page parameter, adding no meaning beyond the schema, which already explains the site vs api source behavior and page limits.

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?

"List the videos Dailymotion relates to a video" gives a specific verb and resource, and the 'related' framing separates it from sibling lists like dailymotion_user_videos_list or dailymotion_videos_search. It stops short of naming any sibling directly, so differentiation is inferred rather than stated.

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?

"Requires `videoId`" implies the prerequisite for use, but there is no statement of when to prefer this over category/user/hashtag video lists, or when the related list is not what the user wants. Usage is implied only.

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