Skip to main content
Glama

google_api_call

Destructive

Invoke Google Workspace REST methods by Discovery ID when no dedicated tool exists; use it for uncovered API operations and return JSON responses.

Instructions

Invoke any Google Workspace REST method by Discovery id (escape hatch for operations without a dedicated tool). Find methods with google_api_search first. A write asks the connected human to confirm the real call (account, verb, params, a destinations-first body summary) unless GOOGLE_PROFILE=full-writes with no outbound allowlist; GOOGLE_READ_ONLY or a matching GOOGLE_WRITE_DENY still refuse outright. On reads, pass a fields query param (Google partial response) to keep the payload small. Returns JSON only; for binary/file content (media downloads, drive.files.export) use drive_download / drive_export instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api": "<api>",
      "methodId": "<methodId>"
    },
    "name": "google_api_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiYesAPI alias: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, analyticsadmin, analyticsadmin_v1alpha, analyticsdata, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents
bodyNoJSON request body
accountNoGoogle account alias (omit for the default account)
methodIdYesDiscovery method id, e.g. "drive.revisions.list"
pathParamsNoValues for {placeholders} in the method path
queryParamsNoQuery-string parameters; use an array for repeated params (e.g. resourceNames)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.2.0
    • changedInput schema / properties / api / description
      Previous value: -"API alias: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, analyticsadmin, analyticsdata, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents"New value: +"API alias: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, analyticsadmin, analyticsadmin_v1alpha, analyticsdata, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents"
  2. Changed9 schema fields changedv5.4.1
    • changedInput schema / properties / account / description
      Previous value: -"Google account alias"New value: +"Google account alias (omit for the default account)"
    • changedInput schema / properties / api / description
      Previous value: -"API alias: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents"New value: +"API alias: gmail, drive, calendar, sheets, docs, slides, forms, people, searchconsole, tasks, chat, meet, driveactivity, drivelabels, admin_directory, admin_reports, admin_datatransfer, groupssettings, analyticsadmin, analyticsdata, appsmarket, classroom, cloudidentity, cloudsearch, groupsmigration, keep, licensing, postmaster, reseller, script, vault, workspaceevents"
    • addedInput schema / properties / api / maxLength
      Added value: +64
    • addedInput schema / properties / methodId / maxLength
      Added value: +256
    • addedInput schema / properties / methodId / minLength
      Added value: +1
    • removedInput schema / properties / pathParams / additionalProperties / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / pathParams / additionalProperties / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • changedInput schema / properties / queryParams / additionalProperties / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        },
      -        {
      -          "type": "boolean"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number",
      +        "boolean"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / required
      Previous value: -[
      -  "account",
      -  "api",
      -  "methodId"
      -]New value: +[
      +  "api",
      +  "methodId"
      +]
  3. First observedv0.0.0-semantically-released

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the human-confirmation flow for writes (account, verb, params, destinations-first body summary), the GOOGLE_PROFILE=full-writes exception, and that GOOGLE_READ_ONLY or GOOGLE_WRITE_DENY cause outright refusal. This tells the agent what happens on failure and why, which the destructive/openWorld hints alone cannot convey.

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?

Front-loads the core purpose in the first clause, then layers constraints in a sensible order: discovery, write confirmation, refusal policy, payload tips, return-type caveat. Dense but every sentence carries operational information; the env-var enumeration in one sentence is slightly crowded.

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?

For a six-parameter open-world escape hatch with no output schema, the description covers routing, safety/confirmation semantics, payload sizing, and the return type (JSON only) with a pointer to the binary-capable siblings. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by recommending the `fields` query param (Google partial response) on reads to shrink payloads. It does not explain pathParams vs queryParams interplay or body shaping beyond the destinations summary, so it stops short of a 5.

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?

States a specific verb and resource ('invoke any Google Workspace REST method by Discovery id') and explicitly frames itself as the escape hatch for operations lacking a dedicated tool, which separates it from the sibling discover tools and dedicated per-service tools.

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?

Gives explicit routing: find method ids with google_api_search first, use this only when no dedicated method tool exists, and use drive_download / drive_export for binary or file content instead. Both the when and the when-not are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.