Skip to main content
Glama

FoxAPIs data sources

YouTube video

youtube_video
Read-onlyIdempotent

A YouTube video's title, channel name and thumbnail, from its link (view counts and dates are not returned). Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": "youtube_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://www.youtube.com/watch?v=jNQXAC9IVRw"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely non-derivable behavior: a 2-credit charge per call, no charge when the answer contains no data, and a required FoxAPIs key. It does not cover failure modes such as invalid URLs or upstream errors, which keeps it from a 5.

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?

Three compact sentences with the output fields front-loaded, followed by the exclusion note, cost, and auth requirement. Every sentence carries information an agent would otherwise lack, and there is no filler.

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 correctly takes on the burden of listing return fields and stating what is excluded. It also covers auth and billing edge cases. It is slightly thin on error behavior beyond the empty-result case, which is the only remaining gap for a single-parameter read 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?

There is a single required parameter with 100% schema description coverage, including a concrete example URL, so the schema already carries the semantics. The description adds nothing about accepted URL formats (shortened youtu.be links, timestamps, playlist parameters), so it neither compensates nor detracts. 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 description names the exact resource (a YouTube video, keyed by its link) and enumerates the returned fields: title, channel name, thumbnail. It also explicitly negates view counts and dates, which prevents a common false expectation. It stops short of naming the youtube_channel sibling as the alternative for channel-level data, so differentiation is implied by the name rather than stated.

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?

Usage is only implied: the agent must infer that this is the tool for a single video URL as opposed to a channel or a search. There is no explicit when-to-use/when-not or routing to siblings. The credit-cost and no-data-free notes are practical but are billing guidance, not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources