Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List replies to a Dailymotion comment

dailymotion_comment_replies_list
Read-onlyIdempotent

Fetch replies to a specific Dailymotion comment by providing the video ID and comment ID, with pagination support for longer reply threads.

Instructions

List the replies to one comment on a Dailymotion video. Requires videoId and commentId. 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>",
      "commentId": "<commentId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_comment_replies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
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.
commentIdYesRequired. Id of a top-level comment, as returned in `id` by the video comments endpoint. Base64 `=` padding is optional.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds only the pagination cue ('use page when paginated'), which the schema largely already conveys via the page parameter. No auth, rate-limit, or ordering context is offered.

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 scope before the requirements. The trailing clause 'use page when paginated' is close to circular and the least valuable part, but there is no bloated preamble.

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 read-only list tool with no output schema, the description tells the agent what it returns ('a list') and that pagination exists, while the schema carries all six parameters. A comment-reply item's shape is not described, but with annotations covering safety and full schema coverage the definition is sufficient to invoke correctly.

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, commentId, page, context, llm_model and conversation_id are all self-documenting; baseline is 3. The description names the two required identifiers and gestures at pagination but adds no format, id-format, or paging semantics beyond what the schema already states.

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 replies to one comment on a Dailymotion video'), which implicitly separates it from the sibling dailymotion_video_comments_list that would return top-level comments. The scoping to a single comment is precise. It does not explicitly name the sibling it is not, so it stops short of a 5.

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?

The description states prerequisites ('Requires videoId and commentId'), which tells the agent what must be known before calling, but gives no when-to-use versus alternatives and no explicit exclusions (e.g. use video_comments_list to discover comment ids first). Usage is implied from the name rather than guided.

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