Skip to main content
Glama

Vimeo

by io.github.pipeworx-io

User

user
Read-onlyIdempotent

Fetch a Vimeo user's public profile by user_id or vanity URL name; returns display name, bio, location, follower/following counts, and upload quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioNoUser biography
uriNoUser URI
linkNoProfile link
nameNoUser name
accountNoAccount type
locationNoUser location
metadataNoAdditional metadata
picturesNoProfile picture data
websitesNoAssociated websites
created_timeNoAccount creation timestamp

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "user_id": "user123"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "account": {
+      "description": "Account type",
+      "type": "string"
+    },
+    "bio": {
+      "description": "User biography",
+      "type": "string"
+    },
+    "created_time": {
+      "description": "Account creation timestamp",
+      "type": "string"
+    },
+    "link": {
+      "description": "Profile link",
+      "type": "string"
+    },
+    "location": {
+      "description": "User location",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "name": {
+      "description": "User name",
+      "type": "string"
+    },
+    "pictures": {
+      "description": "Profile picture data",
+      "type": "object"
+    },
+    "uri": {
+      "description": "User URI",
+      "type": "string"
+    },
+    "websites": {
+      "description": "Associated websites",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, etc. The description adds value by listing the returned fields (display name, bio, location, etc.), which complements the safety profile.

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?

Single sentence front-loads the action and result, with no extraneous words.

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?

Given the simple tool with one parameter and an output schema, the description covers purpose, input, and output fields; lacks error handling details but is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description clarifies that the single parameter can be a user_id or vanity URL, adding meaning beyond the empty schema description, compensating for 0% coverage.

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?

The description clearly states the verb 'Fetch', resource 'Vimeo user's public profile', and scope 'by user_id or vanity URL name', distinguishing it from sibling tools like user_videos.

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?

The description implies usage context (by user_id or vanity URL) but lacks explicit guidance on when to use this tool vs alternatives such as user_videos.

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

All Vimeo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates, and the polymarket_* family has six tools with blurred boundaries. The Vimeo tools are distinct, but the massive unrelated Pipeworx set creates ambiguity about which tool is appropriate for a given task.

Naming Consistency2/5

Tool names mix conventions: Vimeo tools use bare nouns (video, channel, user), while Pipeworx tools use verb_noun (resolve_entity, validate_claim) or noun_verb (ai_visibility_check). Some names like ask_pipeworx and pipeworx_feedback do not follow a consistent verb-first pattern.

Tool Count2/5

40 tools is far too many for a Vimeo server; only 9 tools are Vimeo-related, and the remaining 31 are an unrelated Pipeworx data toolkit. This inflates the surface area and makes the set unwieldy.

Completeness2/5

The Vimeo surface covers read operations (search, get, list) but lacks any write operations like upload, update, or delete videos. It also misses common Vimeo features like comments, likes, or portfolio management, so common tasks would hit dead ends.

Resources