Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo video

vimeo_video_get
Read-onlyIdempotent

Fetch a Vimeo video's metadata by ID—title, description, dates, tags, thumbnails, owner, embed permission, and public counts—to support content research or verification.

Instructions

Get a Vimeo video: title, description, dates, tags, thumbnails, owner, embed permission and public counts. Requires videoId.

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": {
      "videoId": "<videoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_video_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
videoIdYesRequired. Vimeo video id, e.g. `76979871`.
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
Behavior4/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 fully covered. The description adds genuine behavioral value by disclosing exactly which fields come back, which is more than the annotations provide, though it says nothing about auth, quota or behavior for a missing/private video.

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 sentences, front-loaded with the resource and its returned fields. The trailing 'Requires `videoId`' is redundant against the schema's required list, but it costs little and the whole definition is easy to scan.

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?

With no output schema, the description correctly compensates by enumerating the return payload, and it flags the required identifier. It is complete enough to call, with only edge-case behavior (invalid/private video, pagination-free single record) left unstated.

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 all four parameters including videoId, context, llm_model and conversation_id are documented in the schema itself. The description's 'Requires `videoId`' merely restates the required-parameter constraint without adding syntax or semantic detail, so the baseline of 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?

Specific verb and resource ('Get a Vimeo video') followed by an enumeration of the returned fields (title, description, dates, tags, thumbnails, owner, embed permission, public counts). That field list implicitly separates it from siblings like vimeo_video_captions_get or vimeo_video_embed_get, though no sibling is named explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The field list only implies that this is the metadata fetch, leaving the agent to infer selection criteria against the many vimeo_video_* siblings itself.

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