Skip to main content
Glama
Sign In

Vimeo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Channel

channel
Read-onlyIdempotent

Fetch metadata for a Vimeo channel by numeric ID or slug; returns channel name, description, subscriber count, video count, and privacy settings.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel_id_or_slug": "staffpicks"
    },
    "name": "channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_id_or_slugYes

Output Schema

NameRequiredDescriptionDefault
uriNoChannel URI
linkNoChannel link
nameNoChannel name
userNoChannel owner
privacyNoPrivacy level
metadataNoAdditional metadata
picturesNoChannel picture/banner data
descriptionNoChannel description
created_timeNoCreation timestamp
modified_timeNoLast modified timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "channel_id_or_slug": "staffpicks"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "created_time": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Channel description",
+      "type": "string"
+    },
+    "link": {
+      "description": "Channel link",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "modified_time": {
+      "description": "Last modified timestamp",
+      "type": "string"
+    },
+    "name": {
+      "description": "Channel name",
+      "type": "string"
+    },
+    "pictures": {
+      "description": "Channel picture/banner data",
+      "type": "object"
+    },
+    "privacy": {
+      "description": "Privacy level",
+      "type": "string"
+    },
+    "uri": {
+      "description": "Channel URI",
+      "type": "string"
+    },
+    "user": {
+      "description": "Channel owner",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds value by enumerating return fields (name, description, subscriber count, video count, privacy settings), which annotate the response beyond schema defaults.

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?

The description is a single sentence that front-loads the action and resource, then lists return types. Every word is informative, no redundancy.

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 fetch tool with annotations and an output schema (not shown), the description covers the core return fields. It lacks error handling or rate-limit info, but these are partially covered by annotations. The description is sufficiently complete for a low-complexity tool.

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 0%, so the description must compensate. It clarifies that the parameter accepts a numeric ID or a slug, which is meaningful but not exhaustive (e.g., no format constraints or slug pattern hints). An example is provided but parameter semantics remain minimal.

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 uses a specific verb ('Fetch') and resource ('metadata for a Vimeo channel'), and clarifies input type ('numeric ID or slug'). It lists return fields (name, description, subscriber count, video count, privacy settings), distinguishing it from siblings like 'channel_videos' which focus on video lists.

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 for fetching channel metadata but does not explicitly state when to use this tool versus alternatives such as 'channel_videos' for video content or 'category' for hierarchical browsing. No when-not-to-use or prerequisite guidance is given.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources