Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo user following

vimeo_user_following_list
Read-onlyIdempotent

List the accounts a Vimeo user follows by providing their handle or numeric ID. Use pagination to retrieve large following lists.

Instructions

List the accounts a Vimeo user follows. 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_following_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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the pagination mechanism and the required-input note; it says nothing about result shape, ordering, or whether private accounts are included. That is some added value, but not rich behavioral context.

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 the purpose, with no wasted framing. "Returns a list" is close to redundant given a list-verb already appears in the first sentence, which keeps it just short of a 5.

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 seven-parameter read-only listing tool, the essentials (required user, pagination path) are present, and the bulky context/llm_model/conversation_id parameters are self-documented in the schema. However, with no output schema, the description does not indicate what each followed-account entry contains or the ordering, leaving a real gap for an agent that needs to consume the results.

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 page, limit, cursor, user and the metadata parameters are all fully documented in the schema itself. The description restates the `user` requirement and the cursor convention without adding format or constraint detail beyond what the schema provides, which matches the baseline of 3.

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 uses a specific verb and resource ("List the accounts a Vimeo user follows"), which is clearly distinct from the nearby followers-list variant in intent. It does not explicitly contrast itself with vimeo_user_followers_list, so an agent must infer the direction of the relationship from the wording alone.

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 prerequisite ("Requires `user`") and gives a pagination hint ("use cursor when paginated"), which implies how to page through results. There is no explicit when-to-use vs. when-not-to-use guidance and no named alternative for the inverse relationship listing.

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