Skip to main content
Glama

Vee3

by io.github.Vee3io
OverviewAdmin

tiktok.for_you_feed

Fetch for-you feed videos for a region. Requires region.

Cost = 4 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of videos to return (max 20).
regionYesRegion code (for example us, jp, kr).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
msgNoUpstream status message.
codeNoUpstream status code (0 = success).
dataNoFor-you feed videos from the upstream provider.
processed_timeNoUpstream processing time in seconds.

Schema Changelog

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

  1. Changed5 schema fields changed
    • removedOutput schema / $defs / GetTiktokForYouFeedResponseData
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "cursor": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Pagination cursor when returned by the provider.",
-      "title": "Cursor"
-    },
-    "hasMore": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Whether additional pages are available.",
-      "title": "Hasmore"
-    },
-    "total": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Total result count when provided by the upstream provider.",
-      "title": "Total"
-    }
-  },
-  "title": "GetTiktokForYouFeedResponseData",
-  "type": "object"
-}
    • addedOutput schema / $defs / GetTiktokForYouFeedResponseDataItem
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "title": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Video title or caption.",
+      "title": "Title"
+    },
+    "video_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "TikTok video id.",
+      "title": "Video Id"
+    }
+  },
+  "title": "GetTiktokForYouFeedResponseDataItem",
+  "type": "object"
+}
    • changedOutput schema / properties / data / anyOf
      Previous value: -[
-  {
-    "$ref": "#/$defs/GetTiktokForYouFeedResponseData"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "$ref": "#/$defs/GetTiktokForYouFeedResponseDataItem"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / data / description
      Previous value: -"Capability-specific payload from the upstream provider."New value: +"For-you feed videos from the upstream provider."
    • addedOutput schema / properties / data / title
      Added value: +"Data"
  2. Changed1 schema field changed
    • changedOutput schema / properties / processed_time / anyOf
      Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only adds 'Cost = 4 tokens' and 'Requires region', which are about usage parameters rather than behavioral traits like response format, pagination, or rate limits. The description lacks transparency about what the tool returns or how it behaves.

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?

The description is very concise at two sentences and front-loads the primary purpose. However, the second sentence mixes in cost information that is not a core part of the tool's function, and 'Requires region' is somewhat redundant with the schema. Slightly trimmed wording would earn a 5.

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 tool's simplicity (2 parameters, output schema present), the description covers the essential purpose and a key requirement. It does not explain the notion of 'for-you feed' or regional nuances, but the output schema likely covers return values. The description is mostly complete for a straightforward fetch 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 coverage is 100%, so the baseline is 3. The description adds no new meaning beyond the schema; 'Requires region' is redundant with the required field, and 'Cost = 4 tokens' is unrelated to parameter semantics. No additional context is provided for the 'count' parameter.

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 tool's function with a specific verb ('Fetch'), a resource ('for-you feed videos'), and a scope ('for a region'). It distinguishes itself from sibling tools like tiktok.search_videos or tiktok.user_videos by focusing on the regional for-you feed.

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 description mentions 'Requires region' but does not provide any guidance on when to use this tool versus alternatives, nor does it explain any exclusions or prerequisites beyond the parameter requirement. No alternative tools are referenced.

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

All Vee3 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.

Resources