Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo showcase videos

vimeo_showcase_videos_list
Read-onlyIdempotent

List all videos in a Vimeo showcase, including play counts where available, by providing a showcase ID; use pagination cursors to retrieve every page.

Instructions

List a Vimeo showcase's videos, with play counts on every row where available. Requires showcaseId. 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": {
      "showcaseId": "<showcaseId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_showcase_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.
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.
showcaseIdYesRequired. Vimeo showcase (album) id, e.g. `11959649`.
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.8/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive open-world operation. The description adds partial play-count availability and possible pagination, but most cursor behavior is already documented in the schema and there is little further detail about response contents or service behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, followed by the key requirement and pagination cue in one compact statement. Although some details repeat the schema, every phrase is relevant and there is no distracting prose.

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 straightforward list operation with comprehensive parameter documentation and clear safety annotations, the description supplies the scope, required ID, notable play-count field, and pagination cue needed for invocation. Because there is no output schema, 'Returns a list' is a thin account of the result, and explicit sibling-selection guidance is also absent.

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 documentation for `showcaseId`, paging inputs, and the auxiliary parameters. The description repeats the required ID and cursor continuation without adding formats, constraints, or parameter interactions beyond the schema, so the high-coverage baseline 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 gives a specific verb and resource—listing a Vimeo showcase's videos—and adds the useful detail that rows include play counts where available. The showcase scope distinguishes it in substance from channel, group, and user listings, but it does not explicitly differentiate itself from any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Requiring `showcaseId` provides a concrete precondition, and the cursor note tells the agent how to continue paginated results. It does not explain when to prefer this tool over Vimeo search, browse, or other video-list siblings, so the selection guidance is useful but incomplete.

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