Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dailymotion user

dailymotion_user_get
Read-onlyIdempotent

Retrieve a Dailymotion user's profile, follower and video counts, links, avatars, featured video, and channel fields by user ID, username, or profile URL.

Instructions

Get a Dailymotion user: profile, counts, links, avatars, featured video and channel fields. Requires user.

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

Input Schema

NameRequiredDescriptionDefault
userYesRequired. Dailymotion user id (`x2znl3e`) or username (`abinashkathariya`). Usernames are not case-sensitive; ids are. A profile URL is also accepted.
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.
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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the returned field groups and the user-key requirement, but says nothing about rate limits, auth needs, or error behavior for unknown/private users.

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 purpose and followed by the returned fields. The trailing 'Requires `user`' clause is redundant with the schema's required array, but the total length is small and nothing else is wasted.

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 single-resource read tool with no output schema, the description gives enough of the return shape (profile, counts, links, avatars, featured video, channel fields) to set expectations, and annotations handle the safety profile. It could still note behavior for nonexistent users, but nothing essential is missing.

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 baseline is 3. The description only restates that `user` is required; the richer semantics (id vs username case sensitivity, profile URL acceptance, the analytics-only `llm_model`, and the conversation_id echo rule) live entirely in the schema, not the description.

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 ('Get a Dailymotion user') and enumerates the returned surface: profile, counts, links, avatars, featured video and channel fields. That distinguishes it from the sibling *_list tools (followers, videos, playlists) by resource type, though it never explicitly contrasts with them.

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?

Usage is implied by the resource name: fetch a single user's profile. There is no explicit when-to-use guidance, no statement of when to prefer a *_list sibling, and no prerequisites beyond 'Requires `user`'. An agent can infer the intent but receives no routing help.

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