Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo group

vimeo_group_get
Read-onlyIdempotent

Retrieve a Vimeo group's name, description, logo, thumbnail, creator, counts, and dates using its slug or numeric ID.

Instructions

Get a Vimeo group: name, description, logo, thumbnail, creator, counts and dates. Requires group.

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

Input Schema

NameRequiredDescriptionDefault
groupYesRequired. Vimeo group slug or numeric id, e.g. `creativeapps` or `18850`.
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

A3.7/5.0
Behavior4/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's added value is disclosing the payload contents (logo, thumbnail, creator, counts, dates), which matters because there is no output schema; it still says nothing about error behavior for an unknown slug or rate limits.

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 action and return payload, with no filler. The trailing 'Requires `group`' mildly duplicates the schema's required array but is a cheap reinforcement rather than real bloat.

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?

For a simple single-record read with rich annotations and full schema coverage, the definition supplies what the annotations cannot: the shape of the returned object. Only minor gaps remain (not-found behavior, whether counts are lifetime or current), which is acceptable for this complexity level.

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%, including the pattern and examples for `group` and guidance for context/llm_model/conversation_id, so the schema carries parameter semantics. The description only restates 'Requires `group`' without adding format, resolution, or edge-case meaning, which is the baseline 3 when the schema does the work.

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 and resource ('Get a Vimeo group') and enumerates the returned fields (name, description, logo, thumbnail, creator, counts, dates), which makes the single-resource fetch distinct from list/search siblings such as vimeo_groups_search or vimeo_user_groups_list. It stops short of naming any sibling explicitly, so it does not fully earn a 5.

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: the reader infers 'call this when you have a group slug or id and need that one group's details.' There is no explicit when-to-use/when-not statement and no routing to vimeo_groups_search for discovery versus this tool for retrieval, leaving the agent to infer the boundary.

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