Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo channel subscribers

vimeo_channel_subscribers_list
Read-onlyIdempotent

Lists subscribers for a specified Vimeo channel, returning paginated results you can continue with a cursor. Use it to retrieve channel audience details by slug or numeric channel ID.

Instructions

List the subscribers of a Vimeo channel. 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_subscribers_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.
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.
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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that a list is returned and that cursors should be used for pagination, a minor addition that is largely restated in the schema.

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. Minor redundancy exists in restating the required `channel` and cursor behavior that the schema already declares.

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 read-only list operation with rich annotations and a fully described schema, the description is adequate but minimal: it says nothing about ordering, empty results, or error conditions and lacks an output schema to fall back on.

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 the schema already documents channel, page, limit, cursor and the analytics fields thoroughly. The description's mention of `channel` and cursor adds no meaning beyond what the schema states, so 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 gives a specific verb and resource ("List the subscribers of a Vimeo channel"), which an agent can distinguish from sibling tools like vimeo_channel_videos_list or vimeo_user_followers_list without opening the schema. It is clear but offers no explicit contrast with siblings.

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 `channel`" hints at a precondition, and the cursor note implies pagination usage, but there is no statement of when to choose this tool over alternatives or what happens when no subscribers exist. Usage is only implied.

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