vimeo-mcp

Allow a specific domain to embed a video

allow_embed_domain

Idempotent

Allow a specific domain to embed a video. This only takes effect when the video's embed privacy is set to 'whitelist', so set that with update_video first.

Instructions

Allow a specific domain to embed a video. This only takes effect when the video's embed privacy is set to 'whitelist', so set that with update_video first.

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": {
      "video_id": "<video_id>",
      "domain": "<domain>"
    },
    "name": "allow_embed_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to allow, such as example.com.
`video_id`	Yes	Video id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.0Oct 6, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.1Sep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety/idempotency profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely useful behavioral context: the operation is effectively a no-op unless embed privacy is whitelist. It does not describe auth requirements or the response, but the key precondition is disclosed.

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

Conciseness5/5

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

Two tight sentences with the core action front-loaded and the precondition second. No filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with full schema coverage and annotations, the description supplies the one critical thing the structured fields cannot: the whitelist precondition. Nothing an agent needs to call it correctly is missing.

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 documents both video_id and domain. The description adds no syntax or format meaning beyond 'a specific domain', so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (allow) and resource (a domain to embed a video), and the effect is unambiguous. It is clearly distinguishable from sibling tools like apply_embed_preset or list_embed_presets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names the condition under which the call matters ('only takes effect when the video's embed privacy is set to whitelist') and routes the agent to the predecessor tool ('set that with update_video first'). This is exactly the when-to-use guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.