Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo user groups

vimeo_user_groups_list
Read-onlyIdempotent

Lists the Vimeo groups a specified user belongs to, returning paginated results so you can inspect memberships or continue with a cursor.

Instructions

List the groups a Vimeo user belongs to. 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_groups_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

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the pagination continuation note, with no detail on result shape, ordering, or empty-result behavior.

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 core purpose front-loaded and no filler. The parenthetical '(use cursor when paginated)' is slightly clunky and duplicates schema guidance, but the overall size is appropriate.

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?

For a simple read-only list endpoint with full schema coverage and rich annotations, this is nearly sufficient. The only gap is that an agent gets no hint about what a group object contains or how to choose this tool over the sibling group listings.

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 user, page, limit, and cursor is already documented in the schema. The description's mentions of `user` and cursor merely restate that, 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?

States a specific verb and resource: 'List the groups a Vimeo user belongs to,' which is clearly distinguishable from search-oriented siblings like vimeo_groups_search and from group-scoped siblings like vimeo_group_members_list. It does not explicitly name an alternative, which keeps it just short of a 5.

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 establishes the prerequisite ('Requires `user`') and gives a pagination cue, which is real usage context. However, it never states when to prefer this over vimeo_groups_search or the other user-scoped list tools, leaving the choice to inference from names.

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