Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo embed

vimeo_video_embed_get
Read-onlyIdempotent

Retrieves Vimeo embed details for a video ID, including iframe markup, dimensions, thumbnail, and owner account type. Returns restricted status when the video's embedding is disabled.

Instructions

Get a Vimeo embed: iframe markup, size, thumbnail and the owner's account type; restricted when embedding is off. 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_embed_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
dntNoDo-not-track, as the embed parameter spells it.
hashNoUnlisted-video hash, when the video was shared with one.
colorNoPlayer colour as six hex digits, e.g. `00adef`.
titleNoShow the title in the player.
widthNoFixed width of the embed, in pixels.
bylineNoShow the uploader byline in the player.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
videoIdYesRequired. Vimeo video id, e.g. `76979871`.
autoplayNoAsk for autoplay.
maxWidthNoMaximum width of the embed, in pixels.
portraitNoShow the uploader portrait in the player.
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.
maxHeightNoMaximum height of the embed, in pixels.
responsiveNoAsk for responsive iframe markup.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value: it discloses the shape of the payload (iframe markup, size, thumbnail, owner account type) and that results are restricted when the video owner has embedding disabled.

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 compact clauses, front-loaded with the resource and its return contents, then the restriction. The trailing 'Requires `videoId`' duplicates the schema's required list and is the only wasted phrase.

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?

With 15 parameters and no output schema, the description could do more to signal that most parameters are optional player-appearance controls (color, byline, portrait, responsive). It does cover the return payload and the embedding-off restriction, which are the essentials an agent cannot get from structured fields.

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 every one of the 15 parameters is already documented, including the required videoId, hash and the analytics-only llm_model. The description only restates that videoId is required and adds nothing about the appearance/player flags, 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 names a specific verb and resource ('Get a Vimeo embed') and enumerates what the result contains: iframe markup, size, thumbnail and owner account type. That return-content detail distinguishes it from the metadata-oriented sibling vimeo_video_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it needs embeddable player markup rather than video metadata. The 'restricted when embedding is off' clause gives a failure condition but no explicit when-to-use/when-not-to-use routing against alternatives such as vimeo_video_get.

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