Skip to main content
Glama

FoxAPIs data sources

YouTube channel

youtube_channel
Read-onlyIdempotent

A YouTube channel: name, description, keywords, verification flag and channel id, from its link. 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_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://www.youtube.com/@YouTube"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-derivable behavior: a 2-credit cost per call, no charge for empty answers, and an API-key requirement — all useful for an agent deciding whether to spend the call.

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 payload comes first and the pricing/auth caveats follow in short clauses, with no wasted narration. Minor marketing aside ("free to start") is the only non-essential fragment.

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?

For a single-parameter read tool with no output schema, the description enumerates the response fields, the input source, the cost model and the auth prerequisite — enough for correct invocation. Only a note on error/empty-result handling beyond "no data" is absent.

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 one parameter at 100% schema coverage with a concrete example URL, so the schema does the heavy lifting. The phrase "from its link" is consistent with the schema but adds no format or validation detail beyond it; 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?

"A YouTube channel: name, description, keywords, verification flag and channel id, from its link" states a specific resource and its returned fields, which cleanly separates it from youtube_video even without naming that sibling. It is clear what an agent gets and what input produces it.

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?

"from its link" implies the use case (resolve a channel URL into channel metadata), and the credit/key notes set expectations, but there is no explicit when-to-use guidance or mention of when a sibling such as youtube_video would be the better choice. Usage is implied rather than taught.

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