Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo channel

vimeo_channel_get
Read-onlyIdempotent

Retrieves a Vimeo channel's name, description, logo, creator, counts, and dates using its slug or numeric ID. Use it to inspect channel metadata before fetching content.

Instructions

Get a Vimeo channel: name, description, logo, creator, counts and dates. Requires channel.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds the returned-field list, which is genuinely useful given there is no output schema, but says nothing about error behavior for an unknown slug, rate limits, or whether private channels require auth.

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?

A single compact sentence with the resource and its payload front-loaded and zero filler. It is efficient, though the brevity edges toward under-specification rather than maximal informativeness.

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 simple read-only lookup with fully documented parameters and no output schema, listing the returned fields plus the required identifier covers what an agent needs to call it correctly. Only error and access-condition behavior is unaddressed.

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 the schema already explains that `channel` accepts a slug or numeric id with a format pattern. The description only restates that `channel` is required, adding no meaning beyond the schema, 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 gives a specific verb and resource ('Get a Vimeo channel') and enumerates the returned fields (name, description, logo, creator, counts, dates), so the agent knows exactly what it retrieves. It does not explicitly differentiate from near-siblings like vimeo_group_get or vimeo_user_get, which keeps it from 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?

Beyond 'Requires `channel`', there is no guidance on when to use this versus vimeo_channels_search (to find a channel) or the channel sub-resource tools. No exclusions, prerequisites, or alternatives are stated, leaving usage to inference.

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