Connections

List my files

connections_storage_list_files

Read-only

List the files the member owns across every Connections plane: recordings, transcripts, receipts, attachments, public images, exports and visitor uploads. Newest first. Each file's id works with get_file.

Input Schema

Name	Required	Description
`flow`	No	Only this kind, e.g. call_recording, receipt, form_upload.
`limit`	No	How many files per page (default 25, maximum 100).
`query`	No	Text in the file's name or content.
`cursor`	No	The nextCursor from the previous page.
`person`	No	Linked person to run this call as (first name). Omit to run as the connection's holder.
`project`	No	Workspace to run this call in (id or name).
`entityId`	No	Only files attached to this one record.
`entityType`	No	Only on this kind of record, e.g. contact, deal.
`sourcePlane`	No	Only from this plane, e.g. notes, deals.
`createdAfter`	No	Added at or after this date.
`createdBefore`	No	Added before this date.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 27, 2026

changedInput schema / properties / createdAfter / description

Previous value: -"Optional. ISO date; added at or after it."New value: +"Added at or after this date."

addedInput schema / properties / createdAfter / pattern

Added value: +"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2}(\\.\\d{1,9})?)?(Z|[+-]\\d{2}:?\\d{2})?)?$"

changedInput schema / properties / createdBefore / description

Previous value: -"Optional. ISO date; added before it."New value: +"Added before this date."

addedInput schema / properties / createdBefore / pattern

Added value: +"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2}(\\.\\d{1,9})?)?(Z|[+-]\\d{2}:?\\d{2})?)?$"

changedInput schema / properties / cursor / description

Previous value: -"Optional. The nextCursor from the previous page."New value: +"The nextCursor from the previous page."

changedInput schema / properties / entityId / description

Previous value: -"Optional. Only files attached to this one record."New value: +"Only files attached to this one record."

changedInput schema / properties / entityType / description

Previous value: -"Optional. Only on this kind of record, e.g. contact, deal."New value: +"Only on this kind of record, e.g. contact, deal."

changedInput schema / properties / flow / description

Previous value: -"Optional. Only this kind, e.g. call_recording, receipt, form_upload."New value: +"Only this kind, e.g. call_recording, receipt, form_upload."

changedInput schema / properties / query / description

Previous value: -"Optional. Text in the file's name or content."New value: +"Text in the file's name or content."

changedInput schema / properties / sourcePlane / description

Previous value: -"Optional. Only from this plane, e.g. notes, deals."New value: +"Only from this plane, e.g. notes, deals."

Changed7 schema fields changedOct 26, 2026

changedInput schema / properties / createdAfter / description

Previous value: -"Optional. ISO date or date-time; only files added at or after it."New value: +"Optional. ISO date; added at or after it."

changedInput schema / properties / createdBefore / description

Previous value: -"Optional. ISO date or date-time; only files added before it."New value: +"Optional. ISO date; added before it."

changedInput schema / properties / entityType / description

Previous value: -"Optional. Only files attached to this kind of record, e.g. contact, event, deal."New value: +"Optional. Only on this kind of record, e.g. contact, deal."

changedInput schema / properties / flow / description

Previous value: -"Optional. Only files of this kind, e.g. call_recording, receipt, note_attachment, form_upload, event_cover."New value: +"Optional. Only this kind, e.g. call_recording, receipt, form_upload."

addedInput schema / properties / person

Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Optional. Text to find in the file's name or in what was said/written in it."New value: +"Optional. Text in the file's name or content."

changedInput schema / properties / sourcePlane / description

Previous value: -"Optional. Only files that came from this plane, e.g. main, notes, events, deals."New value: +"Optional. Only from this plane, e.g. notes, deals."

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / project

Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}

AddedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: results are ordered newest first and span all planes rather than one, which affects how the agent interprets an empty or truncated page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each earning its place: scope first, ordering second, handoff to get_file third. No repetition of schema or annotation content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, zero-required list tool with no output schema, the description covers purpose, scope and ordering, while the schema documents every parameter. Only mild gap is no statement of what a page contains or when an empty result is expected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and all 11 parameters, including cursor pagination and the flow/sourcePlane filters, are documented inline. The description adds no parameter-level meaning (e.g. how flow values map to the enumerated kinds), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (files the member owns) and enumerates the covered kinds — recordings, transcripts, receipts, attachments, images, exports, visitor uploads — so the scope is concrete. It does not differentiate from storage_search_google_drive, but it does clarify relative to get_file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Newest first' and 'Each file's id works with get_file' imply a browse-then-fetch workflow and point at the retrieval sibling. There is no explicit when-to-use/when-not guidance versus search_google_drive or list_trash, so the usage is only implied.

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

All Connections tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?