Skip to main content
Glama

get_auth_url

Generate the OAuth2 authorization URL to authenticate and access Google Slides presentations for creating, editing, and managing slide content.

Instructions

Get the OAuth2 authorization URL for Google Slides access

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:138-145 (registration)
    Registration of the 'get_auth_url' tool, including its name, description, and input schema (no required parameters).
    {
      name: 'get_auth_url',
      description: 'Get the OAuth2 authorization URL for Google Slides access',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The main handler function for the 'get_auth_url' tool call, which delegates to the auth service and returns a formatted text response with the authorization URL.
    private async handleGetAuthUrl(): Promise<CallToolResult> {
      const authUrl = this.auth.getAuthUrl();
      return {
        content: [
          {
            type: 'text',
            text: `Please visit this URL to authorize the application:\n${authUrl}`,
          },
        ],
      };
    }
  • Supporting helper method in GoogleSlidesAuth class that generates the actual OAuth2 authorization URL with necessary scopes for Google Slides access.
    getAuthUrl(): string {
      const scopes = [
        'https://www.googleapis.com/auth/presentations',
        'https://www.googleapis.com/auth/drive.file'
      ];
    
      return this.oauth2Client.generateAuthUrl({
        access_type: 'offline',
        scope: scopes,
      });
    }
  • Dispatch case in the main CallToolRequestSchema handler that routes 'get_auth_url' calls to the specific handler method.
    case 'get_auth_url':
      return await this.handleGetAuthUrl();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves an OAuth2 URL but doesn't describe what happens after (e.g., redirect flow, token exchange), whether it's idempotent, or any rate limits. For a security-sensitive OAuth2 tool, this is a significant gap in behavioral context.

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?

The description is a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information without unnecessary elaboration.

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

Completeness2/5

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

For an OAuth2-related tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the returned URL looks like, how to use it, or integration with the authentication flow. Given the security context and sibling 'authenticate' tool, more guidance is needed for proper agent usage.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing nonexistent parameters, though it could optionally mention implicit context like user session or scopes if relevant.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('OAuth2 authorization URL for Google Slides access'). It distinguishes from siblings like 'authenticate' by focusing on URL retrieval rather than the full authentication flow. However, it doesn't explicitly differentiate from other potential URL-related tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'authenticate' or other sibling tools. It doesn't mention prerequisites, sequencing, or contextual triggers for OAuth2 URL retrieval, leaving the agent to infer usage patterns.

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/vamsikiran353-gif/google-slides-mcp'

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