Real-Time YouTube Script Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | Yes | Your Tavily API key. | |
| AICREDITS_API_KEY | Yes | Your AICredits or OpenAI key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_info_mcpD | – |
| get_video_script_mcpD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches latest information, the other generates a video script. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern (get_latest_info, get_video_script) with consistent snake_case. The '_mcp' suffix is uniform, maintaining a predictable convention.
With only two tools, the server feels slightly thin for a broad 'Real-Time YouTube Script Generator' purpose. However, the tools cover the core pipeline, making the count borderline but acceptable.
The two tools cover the essential workflow: gathering latest info and generating a script. Minor gaps exist, such as customization or options for script variations, but agents can work around them.