Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo group members

vimeo_group_members_list
Read-onlyIdempotent

Retrieve members of a Vimeo group by group slug or ID, with pagination and cursor support for listing member sets across pages.

Instructions

List a Vimeo group's members. Requires group. 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": {
      "group": "<group>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_group_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-20000. Default: 1. Use `page.nextCursor` to continue; a page past the last is an empty page.
groupYesRequired. Vimeo group slug or numeric id, e.g. `creativeapps` or `18850`.
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 covered. The description adds only the required-parameter constraint and a pagination hint, both of which are largely duplicated in the schema. Nothing is said about ordering, page size defaults, or what a member record contains.

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, requirement first and pagination second, with no wasted wording. It is slightly telegraphic — 'Requires `group`' reads like a note rather than a full sentence — but front-loading is correct.

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 7 parameters (3 required), 100% schema coverage, no output schema and strong annotations, the description covers the minimum needed to invoke the tool. However, for a paginated list tool it omits what a member entry looks like and any hint that context/llm_model are required per-call metadata, leaving the agent to discover that from the schema.

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%, including detailed page/limit/cursor semantics and the group id format, so the baseline is 3. The description's 'use cursor when paginated' restates schema content rather than adding format or constraint detail. No parameter meaning is added beyond the schema.

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 a Vimeo group's members.' That clearly separates it from sibling resources like vimeo_group_videos_list or vimeo_user_groups_list without needing the schema. It stops short of naming a sibling or stating scope boundaries, 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?

'Requires `group`' gives a minimal precondition, and the cursor note implies pagination usage. There is no explicit when-to-use versus alternatives and no statement of when this is the wrong tool (e.g., for user-level group membership, that would be vimeo_user_groups_list). Guidance is implied rather than 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