Skip to main content
Glama
LeomaiaJr

Gemini Docs MCP Server

by LeomaiaJr

Fetch Gemini API Documentation Page

fetch_gemini_doc
Read-onlyIdempotent

Retrieve and parse specific Gemini API documentation pages to access structured content including guides, code examples, and references for features like function calling and embeddings.

Instructions

Fetch and parse a specific Gemini API documentation page.

This tool fetches a documentation page from the Gemini API docs and extracts its content including title, sections, and code examples.

Args:

  • path (string): The documentation path (e.g., "function-calling", "embeddings"). Use empty string "" for the main overview page.

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: Structured data with schema: { "url": string, // Full URL of the page "title": string, // Page title "description": string, // Brief description "sections": [ { "level": number, // Heading level (1-6) "title": string, // Section title "content": string // Section content } ], "codeExamples": [ { "language": string, // Programming language "code": string // Code snippet } ], "fullText": string // Full text content (truncated if too long) }

Common paths:

  • "" (empty) - Main overview page

  • "quickstart" - Getting started guide

  • "function-calling" - Function calling / tool use

  • "embeddings" - Text embeddings

  • "structured-output" - JSON structured output

  • "text-generation" - Text generation basics

  • "image-understanding" - Vision / image analysis

  • "audio" - Audio understanding

  • "live" - Live API (real-time streaming)

  • "api-key" - API key setup

  • "models" - Available models

  • "pricing" - Pricing information

  • "rate-limits" - Rate limits and quotas

Use search_gemini_docs first to find the correct path if you're unsure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDocumentation path (e.g., 'function-calling', 'embeddings', 'quickstart'). Use empty string for the main overview page.
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

The description adds valuable context beyond what annotations provide, including details about what content gets extracted (title, sections, code examples), output format options, and common usage paths. While annotations cover safety and idempotency, the description provides operational context that helps agents understand the tool's behavior in practice.

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 well-structured and front-loaded with the core purpose, followed by organized sections for arguments, returns, common paths, and usage guidance. Every sentence serves a clear purpose with zero waste, making it efficient for both quick scanning and detailed reference.

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

Completeness5/5

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

Given the tool's complexity and the absence of an output schema, the description provides comprehensive context including detailed return structure, common usage examples, and sibling tool guidance. The annotations cover safety aspects, and the description fills in operational details, making this complete for agent understanding.

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?

With 100% schema description coverage, the baseline is 3, but the description adds significant value by providing a detailed return structure for JSON format and listing common path examples. This goes beyond the schema's basic parameter descriptions and helps users understand what to expect from the tool's output.

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

Purpose5/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 specific verbs ('fetch and parse') and resource ('Gemini API documentation page'), distinguishing it from the sibling tool search_gemini_docs. It explicitly mentions extracting content including title, sections, and code examples, providing a comprehensive overview of what the tool does.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives, stating 'Use search_gemini_docs first to find the correct path if you're unsure.' It also lists common paths with examples, helping users understand appropriate contexts for usage and when to choose the sibling tool.

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/LeomaiaJr/gemini-docs-skills'

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