Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo showcase

vimeo_showcase_get
Read-onlyIdempotent

Fetches a Vimeo showcase by ID, returning its title, description, thumbnails, owner, and video count so you can inspect album details.

Instructions

Get a Vimeo showcase: title, description, thumbnails, owner and video count. Requires showcaseId.

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

Input Schema

NameRequiredDescriptionDefault
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.
showcaseIdYesRequired. Vimeo showcase (album) id, e.g. `11959649`.
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.3/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 covered. The description adds value by enumerating the returned fields, which matters since no output schema exists, but it says nothing about auth requirements, error cases (e.g. missing or private showcase), or whether the field list is exhaustive.

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 short sentences with zero filler, and the core purpose with its returned fields is front-loaded ahead of the parameter requirement. Nothing could be trimmed without losing information.

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 simple single-object get with rich annotations and full schema coverage, the definition is minimally adequate, and the field list partially substitutes for the absent output schema. However, an agent gets no signal about what a missing/inaccessible showcase returns or whether the enumerated fields are complete.

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 showcaseId with a pattern and example, plus context, llm_model and conversation_id. The description's only parameter note ('Requires `showcaseId`') repeats the schema, adding no new meaning; 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 showcase') and enumerates the returned fields, so the agent knows exactly what it retrieves. It does not distinguish itself from sibling tools such as vimeo_user_showcases_list or vimeo_showcase_videos_list, missing the top-tier 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?

There is no when-to-use guidance and no mention of alternatives; the only usage statement is 'Requires `showcaseId`', which is a parameter restatement rather than context. An agent must infer from the name alone when to pick this over the showcase-list or showcase-videos siblings.

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