Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dailymotion user videos

dailymotion_user_videos_list
Read-onlyIdempotent

List a Dailymotion user's videos with sorting and pagination, and use a creation time window to retrieve results beyond the 1,000-video limit.

Instructions

List a Dailymotion user's videos, with a time window to go past the 1,000-video limit. 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_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
sortNoOrder. Default: recent.
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.
createdAfterNoOnly videos created after this time (ISO 8601 with a time zone). With createdBefore this windows past the 1,000-row limit.
createdBeforeNoOnly videos created before this time (ISO 8601 with a time zone).
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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's contribution is the 1,000-row ceiling and the createdAfter/createdBefore workaround for paging past it — genuine behavioral information an agent could not get from the annotations. It stops short of describing result ordering or error behavior, keeping it at a 4.

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 compact sentences, front-loaded with purpose and immediately followed by the constraint that matters. The trailing parenthetical "use page when paginated" is slightly cryptic and could be clearer, which keeps it just below a 5.

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 9-parameter, 3-required read tool with no output schema, the description supplies the key return shape (a list) and the hard row ceiling, which is exactly the missing piece. The analytics parameters (context, llm_model, conversation_id) are fully documented in the schema, so leaving them out of the description is acceptable.

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 schema already documents every parameter including page, limit, sort, and the date windows. The description reinforces that `user` is required and that the date range is the escape hatch around the 1,000-row cap, but adds no syntax or format detail 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?

The description gives a specific verb and resource ("List a Dailymotion user's videos") with the platform qualifier, which separates it from the vimeo/tiktok/youtube video-list siblings. It doesn't explicitly contrast with dailymotion_videos_search or dailymotion_user_playlists_list, so differentiation is implied by "user's videos" 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?

It signals when the time window matters (to go past the 1,000-video limit) and notes the `user` prerequisite, which is useful context. However, no alternative tool is named and there is no explicit when-not guidance, so the agent must infer that search should be used for keyword queries instead.

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