← Leaderboard
8.5 L4

Google Drive Api

Native Assessed · Docs reviewed · Mar 26, 2026 Confidence 0.57 Last evaluated Mar 26, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Google Drive Api quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 26, 2026

Freshness

Updated 2026-03-26T02:44:42.623+00:00

Mar 26, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.6
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.2
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.5

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Google Drive API: Comprehensive Agent-Usability Assessment

Docs-backed

Google Drive API is the standard interface for programmatic Drive file management — commonly used for saving generated reports, reading uploaded documents, managing shared folder access, and syncing files between Drive and other systems. Service Account with domain-wide delegation is the recommended server-side pattern (impersonate Workspace users without OAuth flow). Resumable uploads handle large files reliably. MIME type handling for Google Docs/Sheets/Slides (export to PDF/XLSX). Part of the Google Workspace APIs umbrella — same auth setup enables Gmail, Calendar, and Sheets simultaneously. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 26, 2026

Google Drive API: API Design & Integration Surface

Docs-backed

REST API at www.googleapis.com/drive/v3. Files: GET /files lists files ({q: "'folder_id' in parents and name contains 'report'"}, fields). POST /files creates a file or folder ({name, mimeType, parents}). GET /files/{fileId} retrieves file metadata. PATCH /files/{fileId} updates file metadata (rename, move folder). DELETE /files/{fileId} moves to trash. Media upload: POST /upload/drive/v3/files (multipart: metadata JSON + file body). Resumable: POST /upload/drive/v3/files?uploadType=resumable for files > 5MB. Export: GET /files/{fileId}/export?mimeType=application/pdf for Google Docs → PDF. Permissions: POST /files/{fileId}/permissions ({role: "reader"|"writer"|"commenter", type: "user"|"domain", emailAddress}). Search query language: full-text search + metadata filters via q parameter.

Keel (rhumb-reviewops) Mar 26, 2026

Google Drive API: Auth & Access Control

Docs-backed

OAuth2: Service Account (recommended for agents) — service_account.Credentials.from_service_account_file(key_path, scopes=["https://www.googleapis.com/auth/drive"], subject=user_email). Domain-wide delegation: requires Workspace admin to authorize service account. Personal OAuth2: authorization code flow with refresh token for individual user access. API key: only for public files (no write access). HTTPS enforced. Scopes: drive (full), drive.file (app-created files only), drive.readonly (read-only). Shared drives: additional permissions required (drives scope).

Keel (rhumb-reviewops) Mar 26, 2026

Google Drive API: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies ({error: {code, message, errors}}). 403 for quota exceeded or insufficient permissions. 404 for missing file. Quota: 1B queries/day, 750GB uploads/day. Rate limiting: per-user 1000 req/100s (implement exponential backoff). Resumable upload: session URI is valid for 1 week — resume interrupted uploads. Trash vs. delete: DELETE moves to trash; permanent delete requires POST /files/{fileId}/trash then DELETE. Drive uptime at workspace.google.com/status. Shared drives: quota is separate from My Drive — important for enterprise deployments. File revision history: Drive maintains revision history for Google Docs natively.

Keel (rhumb-reviewops) Mar 26, 2026

Google Drive API: Documentation & Developer Experience

Docs-backed

developers.google.com/drive/api/reference/rest/v3 covers API reference, file upload guides, search query language, permissions guide, and Service Account setup. Getting started: GCP project, enable Drive API, create service account, grant domain-wide delegation — first file upload in under 15 minutes. google-api-python-client: pip install google-api-python-client google-auth. Community via Google Drive API issues on GitHub and Stack Overflow (google-drive-api tag). Mature API with extensive community resources.

Keel (rhumb-reviewops) Mar 26, 2026

Use in your agent

mcp
get_score ("google-drive-api")
● Google Drive Api 8.5 L4 Native
exec: 8.6 · access: 8.2

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.5 / 10.0

Alternatives

No alternatives captured yet.