Skip to main content
Glama

set_api_keys

Configure API keys to enable LinkedIn Post Generator to create post drafts from YouTube video transcripts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
openaiApiKeyYesYour OpenAI API key
youtubeApiKeyNoYour YouTube API key (optional)

Implementation Reference

  • src/server.js:19-55 (registration)
    Registration of the 'set_api_keys' tool using McpServer.tool(). Includes input schema with Zod validation, the complete async handler function, and tool description.
    server.tool(
      "set_api_keys",
      { 
        openaiApiKey: z.string().min(1).describe("Your OpenAI API key"),
        youtubeApiKey: z.string().optional().describe("Your YouTube API key (optional)")
      },
      async ({ openaiApiKey, youtubeApiKey }) => {
        try {
          apiKeyManager.setOpenAIKey(openaiApiKey);
          if (youtubeApiKey) {
            apiKeyManager.setYouTubeKey(youtubeApiKey);
          }
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                success: true,
                message: "API keys set successfully. You can now use the other tools."
              }, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                success: false,
                error: error.message
              }, null, 2)
            }],
            isError: true
          };
        }
      },
      { description: "Set your API keys for OpenAI and YouTube (optional)" }
    );
  • Handler function that receives API keys, calls ApiKeyManager.set* methods, and returns MCP-formatted text response with JSON payload indicating success or error.
    async ({ openaiApiKey, youtubeApiKey }) => {
      try {
        apiKeyManager.setOpenAIKey(openaiApiKey);
        if (youtubeApiKey) {
          apiKeyManager.setYouTubeKey(youtubeApiKey);
        }
        
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              success: true,
              message: "API keys set successfully. You can now use the other tools."
            }, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              success: false,
              error: error.message
            }, null, 2)
          }],
          isError: true
        };
      }
    },
  • Zod-based input schema for the tool: requires OpenAI API key as non-empty string, optional YouTube API key.
    { 
      openaiApiKey: z.string().min(1).describe("Your OpenAI API key"),
      youtubeApiKey: z.string().optional().describe("Your YouTube API key (optional)")
    },
  • Helper method in ApiKeyManager class to validate and store the OpenAI API key, called from the tool handler.
    setOpenAIKey(key) {
      if (!key || typeof key !== 'string' || key.trim() === '') {
        throw new Error("Invalid OpenAI API key");
      }
      this.openaiApiKey = key.trim();
      console.log("OpenAI API key set successfully");
    }
  • Helper method in ApiKeyManager class to validate and store the YouTube API key (optional), called from the tool handler.
    setYouTubeKey(key) {
      if (!key || typeof key !== 'string' || key.trim() === '') {
        throw new Error("Invalid YouTube API key");
      }
      this.youtubeApiKey = key.trim();
      console.log("YouTube API key set successfully");
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NvkAnirudh/LinkedIn-Post-Generator'

If you have feedback or need assistance with the MCP directory API, please join our Discord server