Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Vimeo videos

vimeo_videos_search
Read-onlyIdempotent

Search Vimeo videos by keyword and filter by sort order, Creative Commons license, or trending status, with pagination for continuing results.

Instructions

Search Vimeo videos by term, with sort, licence and trending filters. Optional inputs: query, sort, license, trending, page and 2 more. 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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-400. Default: 1. Use `page.nextCursor` to continue; a page past the last is an empty page.
sortNoOrder of the results. Ignored with `trending=true`. One of: relevant, date, alphabetical, plays, likes, comments, duration.
limitNoRows per page, 1-100. Default: 25.
queryNoSearch term, e.g. `cats`. Required unless `trending=true`; ignored with `trending=true`.
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.
licenseNoCreative Commons filter: `CC` (any) or `CC-BY`.
trendingNoReturn the trending videos instead of a query match. `query` and `sort` are ignored. Cannot be combined with `license`.
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.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the return shape (a list) and a cursor hint, but omits auth needs, rate limits, and, critically, that the first call establishes a conversation_id before any parallel calls are allowed.

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

Conciseness3/5

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

Two tight sentences, but "and 2 more" is pure filler that neither informs nor orients the reader about the remaining parameters. The useful content (pagination hint) is buried in a parenthetical at the end rather than front-loaded.

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 ten-parameter, no-output-schema tool, the description omits any mention of the meta parameters (context, llm_model, conversation_id) that dominate the required set and drive call sequencing. An agent leaning on the description alone would not know about the conversation_id handshake, though the schema does spell it out.

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 each of the ten parameters is already documented with constraints, enums, and interactions such as `query`/`sort` being ignored when `trending=true`. The description's partial list ("query, sort, license, trending, page and 2 more") adds no semantics beyond the schema and undercounts the actual parameters.

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?

"Search Vimeo videos by term, with sort, licence and trending filters" gives a specific verb (search) plus resource (Vimeo videos) and scope. It stops short of contrasting with the similarly-named browse/list siblings, so an agent must infer that this one is term-driven rather than channel/user-driven.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative is named despite near-identical siblings such as vimeo_videos_browse or vimeo_user_videos_list. Worse, it lumps `query` under "Optional inputs" while the schema says it is required unless `trending=true`, which points the agent the wrong way.

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