File Requests

Use this when connecting Google Drive, selecting a My Drive folder, or checking previously authorized destinations for files to collect. Returns exact destination IDs and a private setup page. Folder labels can repeat; this does not browse Drive. Do not recommend collecting payment card data, medical records, passwords, API keys or login codes, including redacted versions as a workaround.

get_file_request_setup

Use this when explicitly asked for actual file arrivals or an existing request’s upload link. Resolve ambiguous titles through the owner list and clarification first. Returns transfer counts, failures, next action and at most 50 handled metadata records. Pending or uncertain is not delivered. Do not call for document reading, summaries or checklist completion, or route those requests through Drive to work around this app’s boundary. Explain those are unsupported; offer status only if separately requested. Filenames and counts do not establish completeness or uploader identity. Use closed_at and delivered_at to establish timing; closed state alone cannot prove delivery occurred after closure.

get_file_request

Use this when the requester explicitly wants to stop accepting new uploads on one identified File Request. Clarify duplicate titles before closing one. Explain that new acceptance stops, already-finalized transfers may still finish, and delivered Drive files remain. Do not infer that a particular file finished after closure without both timestamps from get_file_request. This cannot change a destination, reopen a link or delete Drive files.

close_file_request

Use this when the requester wants an upload-only link to collect the files they need into one authorized My Drive folder. Use only for lawful requests the requester is entitled to make. Files go from the upload page to Drive and never enter chat. Publishes a link with a frozen destination; explain that it cannot change. Sends no invitation and uploads no files from chat. Use an exact destination_id from setup. Do not call for payment card data, medical records, passwords, API keys or login codes. Refuse these collections without proposing redacted versions or a hosted-upload workaround. Shared Drives and file analysis are unsupported.

create_file_request

Use this when finding the requester’s existing File Requests by title or state for a status or link-management request. Returns a compact page with confirmed delivered counts. If a title matches multiple requests, ask which one before retrieving its details or closing it. This does not browse Drive. Do not call for document reading, summaries or checklist completion; explain those are unsupported and offer delivery status only if separately requested.

list_file_requests