Gemini Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_gemini_docsA | Search the Gemini API documentation for relevant pages. This tool searches through the Gemini API documentation index to find pages matching your query. It searches across page titles, categories, and keywords to find the most relevant documentation. Args:
Returns: For JSON format: Structured data with schema: { "query": string, // The search query "total": number, // Number of results found "results": [ { "title": string, // Page title "path": string, // Documentation path (e.g., "function-calling") "url": string, // Full URL to the documentation page "category": string, // Category (e.g., "Core Capabilities") "matchedKeywords": [] // Keywords that matched the query } ] } Examples:
Use this tool first to find relevant documentation pages, then use fetch_gemini_doc to get the full content. |
| fetch_gemini_docA | 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:
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:
Use search_gemini_docs first to find the correct path if you're unsure. |
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 with no overlap: fetch_gemini_doc retrieves and parses specific documentation pages, while search_gemini_docs searches across the documentation index to find relevant pages. The descriptions explicitly guide users to use search first when unsure of the path, then fetch for detailed content, creating a logical workflow without confusion.
Both tools follow a perfect verb_noun pattern with consistent snake_case naming: fetch_gemini_doc and search_gemini_docs. The naming clearly indicates the action (fetch/search) and the target (gemini_doc/gemini_docs), making them predictable and easy to understand as a set.
With only 2 tools, this server feels thin for a documentation exploration domain. While the tools cover the core workflow of search-then-fetch, additional operations like listing available documentation categories or getting metadata about the documentation set would enhance completeness. The count is borderline minimal but functional.
For a documentation server, the surface covers the essential workflow: searching for relevant pages and fetching detailed content. The main gap is the lack of a tool to browse or list available documentation sections without searching, which could help agents discover content. However, the search tool with its comprehensive examples mitigates this gap reasonably well.