Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo user likes

vimeo_user_likes_list
Read-onlyIdempotent

List the videos a Vimeo user liked, including like times when available, by providing the user handle or ID. Supports pagination for complete results.

Instructions

List the videos a Vimeo user liked, with the like time when known. Requires user. 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": {
      "user": "<user>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_user_likes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-20000. Default: 1. Use `page.nextCursor` to continue; a page past the last is an empty page.
userYesRequired. Vimeo user: a vanity handle (`staff`), a numeric id (`152184`), or `user<id>` (`user185091330`).
limitNoRows per page, 1-100. Default: 25.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds two useful behavioral facts beyond that: the response includes like times when available, and it is a paginated list that must be walked with a cursor. It says nothing about ordering, empty-result behavior, or privacy restrictions on likes.

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?

Three short sentences, front-loaded with what is returned before the requirement and pagination note. 'Requires `user`' is slightly redundant given the required array, which keeps it from a 5, but there is no filler.

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?

With seven parameters, three of them boilerplate context/llm_model/conversation_id fields, and no output schema, the description is adequate but thin. It doesn't explain the shape of returned items, ordering of likes, or what happens with a private user, which an agent would benefit from knowing when no output schema exists.

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 all seven parameters are already documented in the schema, including the cursor/page.nextCursor relationship and the accepted user formats. The description only restates that `user` is required and echoes the cursor hint, adding no format or constraint detail the schema doesn't already supply — 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 states a specific verb and resource — 'List the videos a Vimeo user liked' — and adds that like timestamps are included when known. That inverts the direction of the sibling vimeo_video_likes_list (users who liked a video), though the description never names the sibling to make the contrast explicit.

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 says 'Requires `user`', which establishes a prerequisite but is already enforced by the schema's required list. There is no guidance on when to prefer this over vimeo_video_likes_list or vimeo_user_videos_list, and no exclusions or edge cases are stated.

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