Skip to main content
Glama
Sign In

openai-sora

by com.jojapi
OverviewDiscussionsAdmin

v2 / Feed

get_v2_feed

v2 / Feed Group: v2 / Explore. Billing per call: 1 Credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cutNoSorting parameter. Default is `nf2`. What does it mean? : - `nf2` : For you (You can assume that it brings random popular videos.) - `nf2_top` : Top videos - `nf2_latest` : Latest videos
limitNoResult limit
cursorNoYou can get subsequent results by entering the `cursor` value taken from the first response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

The description mentions billing ('1 Credits'), which is a behavioral trait, but it does not state whether the operation is read-only, its side effects, or any rate limits. The absence of annotations places the onus on the description, which is only partially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief but not well-structured—'v2 / Feed Group: v2 / Explore' is a header-like string that adds little value. The billing line is useful but the overall structure feels like a placeholder.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and the description does not indicate what the tool returns or how the response is structured. It lacks sufficient context to understand the tool's full scope, especially in comparison to the sibling feed tools.

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?

The schema already provides full descriptions for all three parameters, including the meaning of 'cut' and the cursor usage. The tool description adds no additional insight, so the parameter semantics are adequately handled by the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'v2 / Feed Group: v2 / Explore' is cryptic and does not clearly state what the tool does. It fails to describe an action (e.g., retrieve or list) and merely echoes the tool name.

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?

There is no guidance on when to use this tool versus its siblings (e.g., get_v1_feed_home). No mention of typical use cases or scenarios where this feed is preferred.

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

All openai-sora 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