Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Vimeo users

vimeo_users_search
Read-onlyIdempotent

Search Vimeo users by keyword to find profiles and creators matching your query. Returns paginated results with follower sorting and cursors for continuing to the next page.

Instructions

Search Vimeo users by term. Requires query. Returns a list (use cursor 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": "vimeo_users_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-400. Default: 1. Use `page.nextCursor` to continue; a page past the last is an empty page.
sortNoOrder of the users. One of: followers.
limitNoRows per page, 1-100. Default: 25.
queryYesRequired. Search term, e.g. `cats`.
cursorNoOpaque cursor, 1 to 512 characters. Pass `page.nextCursor` from the previous response to get the next page; omit it to start at the first page. It is tied to the other filters.
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

B3.4/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 bar is lowered. The description adds the return shape ("Returns a list") and the cursor continuation hint, which is genuine extra value, but says nothing about rate limits, ordering defaults, or result size caps.

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 action and followed by the required-param and pagination facts. No filler, though it is terse enough that the pagination note reads as an afterthought rather than structured guidance.

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?

The tool has 8 parameters, including meta parameters (context, llm_model, conversation_id) that carry sequencing and identity constraints the description ignores entirely. The schema does document them, so an agent can still call correctly, but the description contributes little for a tool of this complexity and there is no output schema to lean on beyond "Returns a list."

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 documents query, page, limit, cursor, sort, context and llm_model in detail. The description only restates that query is required and that cursor paginates, adding essentially nothing beyond the structured fields; the 3 baseline 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?

States a specific verb and resource ("Search Vimeo users") and the search term it operates on, which separates it from vimeo_videos_search and vimeo_channels_search by resource alone. It stops short of explicitly contrasting with siblings, so it is clear but not fully differentiated.

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?

The only guidance is "Requires `query`" and "use cursor when paginated," which is implied usage rather than explicit when-to-use. It never says when a caller should prefer this over vimeo_videos_search or the other users_search siblings, and offers 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