Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dailymotion short video feed

dailymotion_feed_shorts_list
Read-onlyIdempotent

Fetches a feed of Dailymotion short videos for a specified country. Use it to discover regional short-form video content and trends by ISO country code.

Instructions

List a feed of Dailymotion's short videos for a country. Optional inputs: country. Returns a list.

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_feed_shorts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter ISO 3166-1 country code, e.g. `US`, `GB`, `FR`. Default: `US`.
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

C2.9/5.0
Behavior2/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 fully covered by structured data. The description adds almost nothing on top: 'Returns a list' is the only return information, and there is no mention of pagination, cursor/limit behavior, feed freshness, or whether results are personalized or region-restricted.

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?

It is short and front-loaded, but the second sentence is largely filler: 'Optional inputs: `country`' restates the schema and 'Returns a list' is near-tautological for a tool named `..._list`. Those two clauses could be dropped or replaced with genuinely useful information.

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 simple read-only feed tool with no output schema and fully documented parameters, the definition is minimally adequate. The notable gap is the return payload: without an output schema, the description should indicate what a feed item contains or how pagination works, and it does neither.

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 coverage is 100% and every parameter carries a description, including the ISO 3166-1 pattern, the default `US`, and the `context`/`llm_model`/`conversation_id` conventions. The description only repeats that `country` is optional, adding no syntax or semantics beyond the schema, so the 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 names a specific verb and resource ('List a feed of Dailymotion's short videos') and adds a scoping dimension ('for a country'), which lets an agent separate it from the video-, channel-, and hashtag-oriented Dailymotion siblings. It stops short of naming a competing shorts/trending feed tool, so differentiation is good but not explicit.

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 when-to-use guidance at all: nothing says when to pick this over `youtube_channel_shorts_list`, `tiktok_feed_trending_list`, or the other Dailymotion list tools, and no prerequisites or exclusions are stated. Only the implicit 'it lists a shorts feed' meaning is conveyed.

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