Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dailymotion users

dailymotion_users_search
Read-onlyIdempotent

Search Dailymotion users by name and filter results to partners or verified accounts. Returns paginated lists for profile discovery and outreach.

Instructions

Search Dailymotion users by name, optionally only partners or verified users. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dailymotion_users_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100). Default: 1. A list never reaches past 1000 rows.
sortNoOrder. Default: relevance.
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.
queryYesRequired. Search term, up to 150 characters. Any language.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
partnerNoSet to `true` to keep only Dailymotion partners.
verifiedNoSet to `true` to keep only verified users.
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, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds only that results come back as a list and that `page` drives pagination; it says nothing about whether searching consumes quota, how empty results look, or the shape of a returned user record.

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 with the resource and filter options front-loaded and no filler. The trailing parenthetical "use page when paginated" is slightly circular, which keeps it from a 5.

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?

With a fully documented 9-parameter schema and complete annotations, the description needs only to confirm purpose, requirement and return shape, which it does. The lack of an output schema leaves the fields of a returned user record unexplained, but that is a modest gap given the schema's richness.

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 every parameter including the unusual context, llm_model and conversation_id fields is already documented in the schema. The description echoes query, partner, verified and page but adds no format or precedence detail 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 gives a specific verb and resource ("Search Dailymotion users by name"), which is clearly distinct from siblings like dailymotion_videos_search or dailymotion_user_get. It does not explicitly name an alternative or state the boundary against a single-user fetch, so it stops short of full sibling differentiation.

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 required input ("Requires `query`") and notes the filter intent (partners/verified) plus a pagination hint, which implies when to use it. There is no explicit when-not guidance, no mention of the single-user alternatives, and no prerequisites or rate/scope limits.

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