Google Workspace · Files

GOOGLE_DRIVE_LIST_FILES

List or search Google Drive files from the connected Google Workspace account. Returns { files, nextPageToken }.

Access
Read
Category
Files
Version
v1

Input schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Optional Drive search query. Defaults to non-trashed files."
    },
    "pageSize": {
      "type": "number",
      "description": "Max files to return (default 10)."
    },
    "pageToken": {
      "type": "string",
      "description": "Optional page token from a prior response."
    }
  },
  "additionalProperties": false
}

How to call it

Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls google_drive_list_files with arguments matching the schema above.

CybrLink validates the input, injects the connected Google Workspace credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.

Frequently asked

How do I let an AI agent google drive list files?
Connect Google Workspace to CybrLink, then expose the `google_drive_list_files` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Google Workspace credential server-side and runs one scoped API call. List or search Google Drive files from the connected Google Workspace account. Returns { files, nextPageToken }.
Does the AI model see my Google Workspace credentials when using GOOGLE_DRIVE_LIST_FILES?
No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from Google Workspace without the OAuth token or API key ever entering its context.