Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dailymotion user playlists

dailymotion_user_playlists_list
Read-onlyIdempotent

List a Dailymotion user's playlists by providing the user ID, username, or profile URL; use pagination to retrieve additional playlist rows.

Instructions

List a Dailymotion user's playlists. Requires user. 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": {
      "user": "<user>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_user_playlists_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
userYesRequired. Dailymotion user id (`x2znl3e`) or username (`abinashkathariya`). Usernames are not case-sensitive; ids are. A profile URL is also accepted.
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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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 by structured data. The description adds only that the call returns a list and that paging applies, without describing response shape, pagination limits, or ordering; that is modest added value beyond the annotations.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence's 'use page when paginated' is slightly circular but is brief enough not to be wasteful.

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 read-only list tool with six parameters, three of them analytics/conversation plumbing fully documented in the schema, the description is adequate but thin. It omits the 1000-row pagination ceiling and default page size that the schema describes, and says nothing about result ordering or auth, so it is minimum viable rather than complete.

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%, including detailed semantics for user, page and limit, so the schema carries the parameter burden. The description restates that `user` is required and gestures at `page` but adds no format or edge-case meaning beyond the schema, making the baseline 3 appropriate.

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 a Dailymotion user's playlists') and scopes it to a single user, which separates it from video/comment listing siblings by resource. It does not explicitly name an alternative such as dailymotion_playlist_get or dailymotion_user_videos_list, so it stops short of full sibling differentiation.

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 guidance on when to choose this tool over alternatives (e.g. playlist_get for a single playlist, user_videos_list for videos). The parenthetical 'use page when paginated' is a vague hint rather than a condition an agent can act on.

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