Skip to main content
Glama
LeomaiaJr

Gemini Docs MCP Server

by LeomaiaJr

Search Gemini API Documentation

search_gemini_docs
Read-onlyIdempotent

Search Google's Gemini API documentation for specific topics like function calling, embeddings, or rate limits to find relevant guides and references.

Instructions

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:

  • query (string): Search query to find relevant documentation (e.g., "function calling", "embeddings", "rate limits")

  • max_results (number): Maximum results to return, 1-20 (default: 10)

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

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:

  • "function calling" -> finds Function Calling documentation

  • "embeddings" -> finds Embeddings documentation

  • "authentication" or "api key" -> finds API Keys documentation

  • "rate limits" -> finds Rate Limits documentation

  • "vision" or "image" -> finds Image Understanding documentation

Use this tool first to find relevant documentation pages, then use fetch_gemini_doc to get the full content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query to find relevant documentation pages (e.g., 'function calling', 'embeddings', 'authentication')
max_resultsNoMaximum number of results to return (default: 10)
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?

Annotations already indicate this is a read-only, non-destructive, idempotent operation with a closed world. The description adds valuable context about what gets searched (titles, categories, keywords) and provides concrete examples of search queries that work well, which helps the agent understand practical usage patterns beyond the safety profile covered by annotations.

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

Conciseness4/5

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

The description is well-structured with clear sections (description, args, returns, examples, usage guidance) and appropriately sized. While comprehensive, some information (like the detailed return format specification) might be slightly verbose given there's no output schema, but overall it's efficient and front-loaded with the core purpose.

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 moderate complexity, rich annotations, and 100% schema coverage, the description provides excellent completeness. It covers purpose, usage workflow with sibling tool, parameter examples, and return format details even without an output schema. The examples section adds practical guidance that helps the agent use the tool effectively.

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

Parameters3/5

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

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description adds minimal value beyond the schema, only providing example queries in the 'Examples' section. This meets the baseline of 3 since the schema does the heavy lifting for parameter documentation.

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 searches the Gemini API documentation for relevant pages, specifying it searches across titles, categories, and keywords. It distinguishes from the sibling tool fetch_gemini_doc by indicating this tool finds pages while the sibling gets full content, making the purpose specific and differentiated.

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 explicitly provides usage guidance: 'Use this tool first to find relevant documentation pages, then use fetch_gemini_doc to get the full content.' This gives clear when-to-use instructions and names the alternative tool, helping the agent understand the workflow.

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