Vimeo

Category

category

Read-onlyIdempotent

Fetch metadata for a single Vimeo category by slug; returns category name, icon, subcategories, and featured video count.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`uri`	No	Category URI
`link`	No	Category link
`name`	No	Category name
`slug`	No	Category slug
`parent`	No	Parent category if applicable
`metadata`	No	Additional metadata
`pictures`	No	Category picture data
`description`	No	Category description

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- changedOutput schema / properties / parent / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "slug": "animation"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Category description",
+      "type": "string"
+    },
+    "link": {
+      "description": "Category link",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "name": {
+      "description": "Category name",
+      "type": "string"
+    },
+    "parent": {
+      "description": "Parent category if applicable",
+      "type": "object"
+    },
+    "pictures": {
+      "description": "Category picture data",
+      "type": "object"
+    },
+    "slug": {
+      "description": "Category slug",
+      "type": "string"
+    },
+    "uri": {
+      "description": "Category URI",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the returned field list, which overlaps with the output schema, and says nothing about error behavior for an unknown slug or caching/rate characteristics.

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?

A single sentence with no filler: the action, the scoping constraint ('single', 'by slug'), and the return payload are all front-loaded in one pass. Nothing could be removed without losing information.

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?

The output schema already documents the return shape and the annotations carry the safety profile, so the description only needs to establish purpose, which it does. The remaining gap is routing guidance against the 'categories' and 'category_videos' siblings, which is not addressed.

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 coverage is 0% – the slug property is bare 'string' with no description. The description partially compensates by identifying the parameter as a slug identifier and the schema example shows the kebab-case form ('animation'), but format rules, casing, and sourcing of valid slugs are left implicit.

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 states a specific verb and resource ('Fetch metadata for a single Vimeo category by slug') and scopes it to one item, which implicitly separates it from the plural sibling 'categories'. It stops short of naming siblings such as 'category_videos' to fully disambiguate, so it lands just below the top tier.

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 word 'single' implies this is the lookup-a-specific-category tool versus a listing tool, so usage is inferable. However, there is no explicit when-to-use, when-not-to-use, or pointer to the 'categories'/'category_videos' alternatives, and no mention of how a slug is obtained.

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

All Vimeo tools Inspect

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.