Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo group videos

vimeo_group_videos_list
Read-onlyIdempotent

List videos from a Vimeo group using its slug or numeric ID, with page limits and cursor pagination to retrieve all group content.

Instructions

List a Vimeo group's videos. 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_videos_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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds one genuinely new behavioral fact — pagination continues via cursor — but says nothing about the shape of the returned list or ordering, so it adds modest value rather than rich 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, front-loaded sentences with no filler. 'Requires `group`' partly restates the schema's required array, but it is brief enough not to be wasteful.

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 simple paginated read with full schema coverage and complete annotations, the description is minimally sufficient, and 'Returns a list' gives a bare hint at output in the absence of an output schema. It leaves out anything about result contents or ordering, so it is adequate rather than complete.

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 and group are fully documented in the schema and the description's mention of `group` and cursor is largely redundant. Baseline 3 applies since the schema carries parameter meaning and the description adds no new format or constraint detail.

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 videos'), which cleanly separates it from vimeo_group_get and vimeo_group_members_list by resource type. It does not explicitly name or contrast any sibling, so it stops 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusions. With many overlapping list siblings (vimeo_videos_browse, vimeo_tag_videos_list, vimeo_channel_videos_list), the description never says why an agent should pick this one over those; only the requirement of `group` implicitly narrows the case.

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