Gemini Capabilities

Gemini Capabilities on Google Cloud are the model features, APIs, and platform patterns used to build production generative AI systems with Gemini across text, multimodal input, structured output, tools, memory, grounding, evaluation, batch inference, embeddings, speech, and agents. On Google Cloud, these capabilities are primarily accessed through Vertex AI, Agent Platform, Google Gen AI SDK, REST, BigQuery, Cloud Storage, and related managed services.

Synthesized across 81 notebooks. See the source pages under Notebooks below for line-level grounding.

This area covers how Gemini models are used beyond basic text generation: controlled JSON output, multimodal reasoning over images/audio/video/PDFs, function calling, code execution, grounding, long context, context caching, embeddings, batch prediction, speech generation, agent memory, computer use, and evaluation.

The common engineering pattern is to make the model interaction explicit: configure the project, location, model, tools, safety settings, schemas, media parts, and generation parameters per request; inspect response metadata; and route model outputs into application code, BigQuery, Cloud Storage, Vertex AI Pipelines, Text-to-Speech, or evaluation workflows.

Most notebooks emphasize production constraints: authentication, API enablement, regional availability, quota, token cost, safety blocks, model-specific feature support, and cleanup of billable resources. Reliable systems preserve chat/tool history correctly, validate structured outputs, ground responses when facts matter, and evaluate quality with task-specific metrics.

Canonical workflow

  1. Set up a Google Cloud project, enable the required APIs, authenticate with Application Default Credentials, and configure PROJECT_ID, LOCATION, and any service-specific environment variables.
  2. Choose the appropriate Gemini model and access path for the task, such as Google Gen AI SDK, Vertex AI REST, OpenAI-compatible Chat Completions, Agent Platform, BigQuery ML, or Text-to-Speech APIs.
  3. Prepare inputs deliberately: add system instructions, prompt context, examples, schemas, media parts with correct MIME types, tool declarations, memory scope, grounding source, or batch input tables/files.
  4. Configure generation behavior explicitly, including thinking controls, safety settings, response modalities, response schemas, function-calling mode, media resolution, context caching, or task-specific embedding type.
  5. Run the request or job, using streaming, async, batch prediction, Vertex AI Pipelines, or BigQuery jobs when those execution modes fit latency and scale requirements.
  6. Inspect outputs and metadata, including candidates, parts, function calls, code execution results, grounding metadata, usage metadata, cached token counts, safety ratings, finish reasons, and job status.
  7. Post-process safely in application code: validate JSON, execute trusted tools, return tool responses, synthesize audio, store embeddings, query vector indexes, sample BigQuery outputs, or persist memories.
  8. Evaluate, monitor, and clean up by comparing against references, running Vertex AI Evaluation or custom metrics, polling terminal job states, deleting caches/jobs/agents/buckets/datasets when done, and preserving IAM policies before updates.

Best practices

See Gemini Capabilities - Best Practices for the full distilled guide.

  • Keep model configuration explicit per request with GenerateContentConfig, system_instruction, safety_settings, tools, response_schema, response_mime_type, generation parameters, and model-selection or thinking controls.
  • Use structured output for downstream systems by setting response_mime_type to application/json, defining response_schema or response_json_schema, marking required fields, allowing nullable fields when context may be missing, and validating parsed results.
  • Use low temperature or temperature=0 for deterministic extraction, classification, tool-calling, and code-execution examples; keep Gemini 3+ sampling defaults when the notebook recommends default temperature behavior.
  • Preserve full model response content in manual function-calling or tool histories so thought signatures are retained; prefer SDK chat history or automatic function calling when possible.
  • Declare tools with clear FunctionDeclaration names, descriptions, typed parameters, required fields, and allowed function modes; execute tools only in trusted application code and verify function call names before dispatch.
  • Use grounding when factuality matters: inspect grounding metadata, citations, search queries, retrieval queries, and grounding chunks, and choose Google Search, Enterprise Web Search, Maps, Vertex AI Search, or internal context based on compliance and data needs.

Key models & APIs

  • gemini-3.5-flash, gemini-3.1-pro-preview, gemini-3.1-flash-lite, gemini-3-flash-preview, gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-flash-image, gemini-2.0-flash, gemini-2.0-flash-001, gemini-3.1-flash-tts-preview, gemini-2.5-flash-tts, gemini-embedding-001, gemini-embedding-2, text-embedding-005, gemini-2.5-computer-use-preview-10-2025, model-optimizer-exp-04-09, Google Gen AI SDK, Vertex AI Gemini API, Vertex AI REST API, OpenAI Chat Completions-compatible Vertex AI endpoint, Agent Platform API, Vertex AI Agent Engine, Vertex AI Memory Bank, ADK, Gemini Data Analytics API, Cloud Text-to-Speech API, Vertex AI Evaluation, Vertex AI Pipelines, BigQuery ML ML.GENERATE_TEXT, BigQuery ML ML.GENERATE_EMBEDDING, BigQuery Vector Search, Vertex AI Search, Google Search grounding, Enterprise Web Search grounding, Google Maps grounding, Cloud Storage, BigQuery, LangGraph, LangChain, Playwright

Notebooks (81)

Agents & ADK (2)

Audio (3)

Embeddings & Vector Search (2)

Gemini (72)

SDK (1)

Vision (1)


Part of the Generative AI Google Brain · Gemini Capabilities - Best Practices