Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List videos a Vimeo user appears in

vimeo_user_appearances_list
Read-onlyIdempotent

List videos featuring a Vimeo user by handle or numeric ID; returns paginated results with a cursor to continue.

Instructions

List the videos a Vimeo user appears in. 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_appearances_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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds only that `user` is required and that pagination uses a cursor, which duplicates the schema. It says nothing about what an appearance means (credited vs. tagged vs. cameo), rate limits, or result ordering.

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?

The description is two short sentences with no padding, and the required parameter is front-loaded. The pagination clause is slightly clipped, and it restates what the schema already encodes, but the description is still well within an appropriate size for a list tool.

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 7-parameter, read-only list tool with no output schema, the description covers the resource, the required input, and pagination, which is enough to call the tool. It omits the semantics of 'appears in', mentions nothing about the mandatory context, llm_model, or conversation_id echo protocol, and gives no return-shape detail beyond '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 explains page, limit, cursor, user, context, llm_model, and conversation_id. The description repeats the `user` requirement and hints at cursor use, and it adds no new syntax or format details. A baseline of 3 is appropriate when the schema does the heavy lifting.

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 the videos a Vimeo user appears in.' That is a precise scope, and the word 'appears' sets it apart from an upload or ownership listing. However, the sibling vimeo_user_videos_list is never named or contrasted, so an agent must infer whether the two differ by appearances or by ownership.

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?

'Requires `user`' gives a light prerequisite, and '(use cursor when paginated)' gives minimal usage guidance. The description never states when to choose this tool instead of vimeo_user_videos_list or vimeo_videos_search, and it lists no exclusions. The implied usage is clear enough to call the tool, but the alternatives are not differentiated.

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