Nexscope Ecommerce Data MCP

YouTube Comments

social_youtube_video_comments

Read-only

Fetches comments and replies from a YouTube video, including each comment's text content, author details, like count, reply count, and publish date. publishedTime is a best-effort ISO timestamp calculated from YouTube's relative label, not an exact source timestamp. Supports ordering by top or newest, and paginating with continuationToken. Limited to approximately 1,000 top comments or 7,000 newest comments. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. YouTube Comments API View Pricing Get comments from a video. Can only get 1k top comments and about 7k new comments. 1 credit per request Actual supplier units are reported per request. Examples are not guaranteed prices.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "social_youtube_video_comments"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	YouTube video URL
`order`	No	Order of comments
`continuationToken`	No	Continuation token to get more comments. Get 'continuationToken' from previous response.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real value beyond that: the publishedTime field is best-effort derived from a relative label, results are capped near 1,000 top or 7,000 newest comments, and calls cost credits. The pricing text is internally inconsistent ("at least 10 Nexscope credits" vs. "1 credit per request"), which muddies rather than clarifies the cost model.

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 useful content is front-loaded, but the tail is pasted pricing boilerplate that repeats the comment limits and cost twice ("YouTube Comments API View Pricing...", "Can only get 1k top comments and about 7k new comments. 1 credit per request") and ends with a disclaimer about example prices. Roughly half the text is redundant vendor copy.

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?

With no output schema, the description carries the burden of describing returns, and it does list the returned fields plus the timestamp caveat and result caps. Cost behavior is mentioned but self-contradictory, leaving the one materially ambiguous area for an agent that must decide whether to re-request.

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 100%, so url, order, and continuationToken are already documented in structured fields. The description restates the order and continuation behavior at roughly the same level of detail without adding format or constraint information beyond the schema, so the baseline 3 applies.

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 opening sentence names a specific verb and resource (fetches comments and replies from a YouTube video) and enumerates the returned fields, so an agent knows exactly what it gets. It does not explicitly distinguish itself from the close sibling social_youtube_video_comment_replies, which limits it to a 4.

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 explains that ordering can be top or newest and that continuationToken paginates, which implies usage but never states when to choose this tool over the sibling replies tool or when not to use it. The cost note gives a mild decision signal (repeated requests may purchase data again) but no explicit alternative routing.

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

All Nexscope Ecommerce Data MCP 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.

Resources

Need Help?