Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List comments on a Dailymotion video

dailymotion_video_comments_list
Read-onlyIdempotent

Fetch comments from a Dailymotion video, including each comment's first replies, using the video ID. Page through results to review larger comment lists.

Instructions

List the comments on a Dailymotion video, each with its first replies. 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_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
limitNoTop-level comments per page (1-20). Default: 20. Each comes with its first 5 replies.
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.2/5.0
Behavior3/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 covered. The description adds one genuinely useful behavioral fact beyond that: each top-level comment arrives with its first replies, meaning the payload is partially expanded. It says nothing about ordering, reply depth limits, or what happens past the 1000-row cap.

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?

A single tight sentence plus two short clauses, with the core action and the reply-bundling behavior front-loaded. 'Requires videoId' is mildly redundant with the schema's required list, but nothing else wastes space.

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 six-parameter list tool with no output schema, the description is minimally adequate: it names the resource, notes the inline replies, and points at pagination. It leaves the return structure (field names, reply count cap of 5, page size ceiling of 20) entirely to the schema, and the phrase 'use page when paginated' is vague about when a caller should actually iterate.

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 videoId, page, limit and the required context/llm_model fields are all documented in the schema itself. The description only repeats 'Requires videoId' and gestures at page, adding no syntax, format, or defaulting detail the schema lacks, so the 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?

The description states a specific verb and resource ('List the comments on a Dailymotion video') and adds a scope detail that the top-level comments come bundled with their first replies. That implicitly separates it from dailymotion_comment_replies_list, but it never names a sibling, so an agent must infer the boundary itself.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (dailymotion_comment_replies_list for deeper threads, or the other platform comments tools). The only conditional phrasing, 'use page when paginated,' describes pagination mechanics rather than tool selection.

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