Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo On Demand title

vimeo_ondemand_get
Read-onlyIdempotent

Retrieve a Vimeo On Demand title's metadata by slug, including description, genres, prices, film, trailer, owner, and counts for research or catalog lookup.

Instructions

Get a Vimeo On Demand title: description, genres, prices, film, trailer, owner and counts. Requires slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Vimeo On Demand slug or numeric id, e.g. `pariah`.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds the shape of the payload (which fields come back) and confirms a single slug lookup, but says nothing about auth requirements, rate limits, or error behavior for a missing title.

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, front-loaded with the verb and resource before the required parameter. The field enumeration is dense but each item is informative; nothing is padded or redundant.

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 usefully compensates by listing the returned fields, which is the key missing piece for a read tool. Combined with annotations covering safety and a fully documented schema, an agent has enough to call it correctly; only invocation-adjacent details like errors or auth are absent.

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%, with the slug pattern and example ('pariah') fully documented in the schema, so the baseline is 3. The description only echoes 'Requires `slug`' and adds no new meaning for context, llm_model, or conversation_id.

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 ('Get') and resource ('Vimeo On Demand title') and enumerates the returned data (description, genres, prices, film, trailer, owner, counts), which pins down the endpoint. It does not explicitly contrast with the similarly-named Vimeo siblings such as vimeo_video_get or vimeo_showcase_get, so it stops short of full sibling differentiation.

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?

The only usage instruction is 'Requires `slug`', which restates the schema's required field rather than saying when to call this tool. There is no guidance about when to prefer it over vimeo_video_get or the other Vimeo getters, and no exclusion conditions.

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