Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Vimeo user or tag videos

vimeo_videos_browse
Read-onlyIdempotent

Browse Vimeo videos by user or tag, sort by date, duration, plays, or likes, and page through results with a cursor.

Instructions

List videos from a Vimeo user or tag with sorting and deep paging. Optional inputs: tag, user, sort, page and cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_videos_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoBrowse videos carrying this tag.
pageNoPage number, 1-based. Default: 1.
sortNoOrder of the list. Default: date.
userNoBrowse a user's videos (handle, numeric id or `user<id>`).
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

A3.5/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 covered. The description adds genuine behavioral context by noting deep paging and that the cursor should be used once paginated, but it omits what the `context`/`conversation_id` sequencing implies and says nothing about result caps or how `page` and `cursor` interact.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence spends space re-listing parameter names the schema already documents, which is the only redundancy.

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 read-only browse tool with full schema coverage and no output schema, an agent has enough to call it correctly: what it lists, how to page, and that a list comes back. The remaining gap is the unresolved tag-vs-user relationship, which matters for filter correctness but is a minor omission given how complete the schema is.

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 explains every filter's format, constraints and defaults; baseline 3 applies. The description merely restates the parameter names, and does not clarify the one semantic question the schema leaves open — whether `tag` and `user` are mutually exclusive or can be combined.

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 videos from a Vimeo user or tag') plus scope modifiers ('sorting and deep paging'), so the agent knows exactly what the tool returns. However, it never distinguishes itself from near-identical siblings such as vimeo_tag_videos_list and vimeo_user_videos_list, leaving the agent to guess which one to pick.

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?

The phrase 'from a Vimeo user or tag' implies the caller should supply one of `tag` or `user`, which is usable guidance. But there is no explicit when-to-use framing, no rule for what happens if both or neither are supplied, and no routing to the sibling list tools that appear to cover the same ground.

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