import { z } from 'zod';
/**
 * A file in Drive: any content stored in Drive (a blob, a Google Workspace
 * document, a folder, or a shortcut), identified by an immutable id.
 *
 * Fields here are the MCP toolset's lossy `File` projection of the REST
 * `files` resource (`name` → `title`, `parents[0]` → `parentId`,
 * `owners[0].emailAddress` → `owner`, `webViewLink` → `viewUrl`, `size` →
 * `fileSize`, `capabilities.canAddChildren` → `canAddChildren`), plus the
 * REST-vocabulary flags the methods write (`starred`, `trashed`,
 * `folderColorRgb`, `copyRequiresWriterPermission`, `writersCanShare`). Tools
 * request only the toolset fields, so their outputs stay verbatim to the MCP
 * pages; methods request the superset so a write's effect is visible in its
 * output. Field docs use `.describe()` so they reach the wire JSON Schema an
 * MCP client reads.
 *
 * @see https://developers.google.com/workspace/drive/api/guides/about-files
 */
export declare const File: z.ZodObject<{
    id: z.ZodString;
    title: z.ZodOptional<z.ZodString>;
    parentId: z.ZodOptional<z.ZodString>;
    mimeType: z.ZodOptional<z.ZodString>;
    fileSize: z.ZodOptional<z.ZodString>;
    description: z.ZodOptional<z.ZodString>;
    fileExtension: z.ZodOptional<z.ZodString>;
    contentSnippet: z.ZodOptional<z.ZodString>;
    viewUrl: z.ZodOptional<z.ZodString>;
    sharedWithMeTime: z.ZodOptional<z.ZodString>;
    createdTime: z.ZodOptional<z.ZodString>;
    modifiedTime: z.ZodOptional<z.ZodString>;
    viewedByMeTime: z.ZodOptional<z.ZodString>;
    owner: z.ZodOptional<z.ZodString>;
    canAddChildren: z.ZodOptional<z.ZodBoolean>;
    starred: z.ZodOptional<z.ZodBoolean>;
    trashed: z.ZodOptional<z.ZodBoolean>;
    folderColorRgb: z.ZodOptional<z.ZodString>;
    copyRequiresWriterPermission: z.ZodOptional<z.ZodBoolean>;
    writersCanShare: z.ZodOptional<z.ZodBoolean>;
}, z.core.$strip>;
export type File = z.infer<typeof File>;
//# sourceMappingURL=File.d.ts.map