Skip to main content
Glama
Sign In

Orivale Agent Intelligence

by io.github.tapirro
OverviewDiscussionsAdmin

orivale_youtube_transcript_hooks

Read-onlyIdempotent

Extract video title, channel, timestamped chapters, transcript excerpt, and 3 viral hook angles from a public https:// YouTube/video URL.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https:// YouTube or video URL
x402_paymentNoOptional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public YouTube or video page https:// URL"New value: +"Public https:// YouTube or video URL"
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedInput schema / properties / url / minLength
      Added value: +12
    • addedInput schema / properties / url / pattern
      Added value: +"^https://[^\\s/$.?#].[^\\s]*$"
    • changedInput schema / properties / x402_payment / description
      Previous value: -"Optional Base64 x402 PAYMENT-SIGNATURE"New value: +"Optional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload."
    • addedInput schema / properties / x402_payment / maxLength
      Added value: +8192
    • addedInput schema / properties / x402_payment / minLength
      Added value: +16
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the 'public URL' precondition and reveals that only a transcript 'excerpt' is returned, but it never discloses the payment gate implied by x402_payment unlocking the 'full payload' — a significant behavioral fact left to the schema.

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?

A single front-loaded sentence with zero filler, but the comma-separated output list is dense enough that the partial-vs-full payload distinction is easy to miss.

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

Completeness3/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 explaining return values; it enumerates the fields but not their shape, excerpt length, chapter format, or what the paid tier adds. For a tool whose default output is truncated, that is a meaningful gap.

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 both parameters are already documented in structured fields and baseline is 3. The description restates the URL requirement without adding format, accepted-host, or length guidance, and says nothing about when or how x402_payment should be supplied.

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?

States a concrete verb ('Extract') plus the exact artifacts returned: video title, channel, timestamped chapters, transcript excerpt, and 3 viral hook angles, scoped to public https:// YouTube/video URLs. No sibling in the listed set is a media/transcript tool, so the resource itself distinguishes it, though the description never explicitly contrasts with anything.

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 by the 'public https:// YouTube/video URL' constraint; there is no explicit statement of when to pick this tool, no exclusions (e.g. private/age-gated videos), and no named alternative for related tasks.

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

All Orivale Agent Intelligence 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