Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dailymotion videos

dailymotion_videos_search
Read-onlyIdempotent

Search Dailymotion videos by keyword, category, language, country, tag, duration, or time window to find relevant clips and filter results by live status, sort order, and pagination.

Instructions

Search Dailymotion videos by term, category, language, country, tag, duration and time window. Optional inputs: query, sort, category, language, country and 9 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_videos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNo`onair` for live videos streaming now, `offair` for other live videos. The list can change between requests, so treat an empty `onair` result as unreliable. A row returned for `onair` can still have `onAir` false.
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
sortNoOrder. Default: relevance with a query, otherwise recent. Relevance and old need a query. `old` can start with videos whose `createdAt` is null. Relevance order can shift between pages, so a row can repeat.
tagsNoOne tag the owner set on the video.
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.
queryNoSearch term, up to 150 characters. Any language.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter country code the owner set, e.g. `us`.
categoryNoCategory id, as listed by the channels endpoint (`id`), e.g. `music`, `news`, `auto` (Cars).
languageNoTwo-letter language code the owner set, e.g. `en`.
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.
maxDurationNoLongest video, in minutes.
minDurationNoShortest video, in minutes.
createdAfterNoOnly videos created after this time (ISO 8601 with a time zone, 2005-01-01 or later). With createdBefore this windows past 1,000 rows. A category with a date window and no query can be slow.
createdBeforeNoOnly videos created before this time (ISO 8601 with a time zone, 2005-01-01 or later). With createdAfter this windows past 1,000 rows. A category with a date window and no query can be slow.
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.
includeExplicitNoInclude videos marked explicit. Default: false, as on the site's own search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 safety behavior is covered. The description adds that the result is a list and hints at pagination, which is useful given there is no output schema, but it omits the substantive behavioral facts in the schema (empty `onair` results being unreliable, relevance ordering shifting across pages, slow category+date-window queries).

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

Conciseness3/5

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

Two sentences, front-loaded with the purpose, which is good. However, the middle clause listing five parameters followed by "and 9 more" is pure filler that consumes space without informing the agent, and the parenthetical about `page` is vague.

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?

With 17 parameters and no output schema, the description is thin, but the schema itself is exceptionally detailed (100% coverage) and the annotations cover the safety profile, so the agent can call the tool correctly. What is missing is selection guidance against the many sibling list/search tools, which no structured field supplies.

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 explains every parameter in detail, including enums, defaults, and edge cases. The description's partial enumeration ("`query`, `sort`, `category`, `language`, `country` and 9 more") adds no meaning and is actually inconsistent with the 15 optional parameters present, but per the baseline rule a 3 is appropriate when the schema does the heavy lifting.

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 ("Search Dailymotion videos") and enumerates the filter dimensions (term, category, language, country, tag, duration, time window), so the operation is unambiguous. It does not differentiate itself from siblings such as dailymotion_category_videos_list, dailymotion_hashtag_videos_list, or vimeo_videos_search, which an agent could easily confuse with a general search.

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 statement of when to prefer this tool over the category-, hashtag-, or user-scoped list siblings, nor any exclusions or prerequisites. The only quasi-guidance, "use page when paginated," is circular and tells the agent nothing actionable; the meaningful pagination rules (1000-row cap, page/limit interaction) live only in the schema.

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