Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo channel videos

vimeo_channel_videos_list
Read-onlyIdempotent

List videos from a Vimeo channel using its slug or numeric ID, with pagination and sorting controls to browse or analyze channel content.

Instructions

List a Vimeo channel's videos. Requires channel. 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": {
      "channel": "<channel>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_channel_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.
sortNoOrder of the videos. One of: added, date, plays, likes, comments, duration, alphabetical, manual.
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.
channelYesRequired. Vimeo channel slug or numeric id, e.g. `staffpicks` or `927`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
directionNoDirection of the sort: `desc` or `asc`. Default: `asc` for `sort=alphabetical`, otherwise `desc`; also applied when `sort` is omitted.
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, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the return shape ("Returns a list") and a cursor hint for pagination, without covering rate limits, auth requirements, or what happens when the channel does not exist.

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 purpose and no padding. The middle sentence restates that `channel` is required, which the schema's required array already conveys, so it is slightly redundant but not costly.

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 nine-parameter listing tool with no output schema, the description sketches the return shape only as "a list" and defers all pagination mechanics to the schema. The heavily documented schema compensates for most detail, but nothing explains the shape of list items or the behavior of the required context/conversation_id meta-parameters that an agent must know to call it correctly.

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% and every parameter (page, cursor, sort, direction, limit, channel, plus the meta-parameters) is thoroughly documented in the schema. The description's mentions of `channel` and `cursor` merely repeat that documentation, adding no new syntax, defaults, or edge cases, 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?

The description states a specific verb and resource ("List a Vimeo channel's videos"), and the qualifier "channel's" separates it from siblings like vimeo_group_videos_list, vimeo_user_videos_list and vimeo_tag_videos_list. It stops short of naming those alternatives explicitly, so it is clear but not maximally differentiating.

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 or when-not-to-use guidance and no routing to alternatives such as vimeo_channel_get or vimeo_videos_browse. "Requires `channel`" is a parameter prerequisite, not usage guidance, so the agent must infer the selection criteria from the names alone.

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