Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dailymotion video

dailymotion_video_get
Read-onlyIdempotent

Retrieve Dailymotion video metadata—title, counts, owner, and thumbnails—by passing a video ID or URL.

Instructions

Get a Dailymotion video with title, counts, owner and thumbnails. Requires videoId.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_video_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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. The description adds the useful detail that the response includes title, counts, owner and thumbnails, partially compensating for the absent output schema, but says nothing about rate limits, auth, or pagination.

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, front-loaded with the resource and the payload summary. The second sentence duplicates the schema's required-field information and could be dropped without loss.

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 simple read-only fetch with no output schema, the description gives an adequate sketch of the return shape and the required identifier. The unusual meta-parameters (context, llm_model, conversation_id) are fully documented in the schema, so the description needn't repeat them.

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 the videoId pattern and URL-acceptance note, the context field, the llm_model field and conversation_id. The description's 'Requires `videoId`' merely restates schema content and adds no meaning beyond it, so 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?

Names a specific verb (Get) and resource (Dailymotion video) and previews the returned payload (title, counts, owner, thumbnails). It does not explicitly distinguish itself from sibling getters such as dailymotion_video_transcript_get or dailymotion_playlist_get, so an agent must infer the boundary from the names alone.

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?

The only guidance is 'Requires `videoId`', which is a parameter fact rather than usage guidance. There is no statement of when to pick this tool over the transcript, comments, related, or subtitles siblings, and no exclusions.

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