Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo user

vimeo_user_get
Read-onlyIdempotent

Retrieve a Vimeo user's profile, bio, links, account flags, counts, followers, and last-changed time by handle, numeric ID, or user ID.

Instructions

Get a Vimeo user: profile, bio, links, account flags, counts, followers and last-changed time. Requires user.

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

Input Schema

NameRequiredDescriptionDefault
userYesRequired. Vimeo user: a vanity handle (`staff`), a numeric id (`152184`), or `user<id>` (`user185091330`).
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=true, so the safety profile is covered without the description. The description does add value by naming the fields in the response payload, but it omits failure behavior for unknown/private users and any rate-limit or privacy-redaction notes, which matter for a user-profile endpoint.

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 clauses, front-loaded with the verb and resource, then the return contents. The trailing "Requires `user`" is redundant with the schema's required list and is the one line that does not earn its place.

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 single-resource read with rich annotations, a fully described schema, and no output schema, the description covers what the tool returns and what it needs. It stops short of describing error or privacy behavior, which is the main remaining gap.

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 `user`, so the schema carries the parameter burden. The description's only parameter comment, "Requires `user`," adds nothing beyond `required: ["user"]`, leaving this at the baseline 3.

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 user") and enumerates the profile content returned: bio, links, account flags, counts, followers, last-changed time. That is enough to distinguish it from the sibling list tools (followers_list, videos_list), though it never names an alternative explicitly.

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 guidance is "Requires `user`," which restates a schema requirement rather than saying when to call this tool. There is no mention of when to prefer it over vimeo_user_videos_list or vimeo_user_followers_list, and no stated preconditions or exclusions.

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