Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dailymotion category videos

dailymotion_category_videos_list
Read-onlyIdempotent

List the videos of a Dailymotion category in the platform's own order, using a required category ID. Paginate results to browse beyond the first page.

Instructions

List the videos of a Dailymotion category, in Dailymotion's order. Requires categoryId. 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": {
      "categoryId": "<categoryId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_category_videos_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.
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.
categoryIdYesRequired. Category id, as listed by the channels endpoint (`id`), e.g. `music`, `news`, `auto` (Cars).
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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the notable trait that results come back in Dailymotion's own order (implying no sort control) and that pagination should go through `page`. It says nothing about result volume limits, which are only visible in the schema's page description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence carries purpose, ordering behavior, the required input, and the pagination hint with no filler. The "Requires `categoryId`" clause mildly duplicates the schema's required list but is short enough to earn its place as a precondition warning.

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 full schema coverage and no output schema, the description covers purpose, one required param, and pagination. It does not indicate what a returned list item contains or that the response carries paging state, so an agent calling it blind knows the shape only roughly.

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?

With 100% schema description coverage, the schema already documents categoryId's enum, page's 1-100 range, and the context/llm_model/conversation_id fields. The description only restates that categoryId is required and hints at page usage, adding little meaning beyond the structured data. 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 concrete verb and resource ("List the videos of a Dailymotion category") plus a scope qualifier, "in Dailymotion's order", that distinguishes it from search-style siblings. It does not explicitly name an alternative tool, but the category-scoped framing makes the boundary clear enough without opening a schema.

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 states the hard prerequisite ("Requires `categoryId`") and a conditional hint ("use page when paginated"), which is real usage guidance. It never says when to prefer this over dailymotion_hashtag_videos_list, dailymotion_user_videos_list, or dailymotion_videos_search, and offers no exclusions, so selection guidance is only implied.

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