list_resources

List every resource this credential can see, with each one's address, type and size. Depending on its context, that can include the represented user's own resources, team-owned resources from its bound teams, and resources it can reach in the organization's shared catalogue. Use it to discover what already exists before you read, edit, or copy a resource. It takes no parameters.

What you can see is broader than what you can change: a resource you can reach in the shared catalogue shows up here so you can read and copy it, even if only a person can edit the catalogue itself.

Parameters

None.

Response

Field	Type	Description
resources	array	The resources you can see (see below).

Each entry:

Field	Type	Description
uri	string	The address to pass to get_resource.
name	string	The resource's label.
path	string	The resource's path.
content_type	string	Its MIME type (e.g. text/markdown).
size_bytes	integer	Its size in bytes.

Example

Result:

{
	"resources": [
		{
			"uri": "apistash://me/docs/readme.md",
			"name": "readme.md",
			"path": "docs/readme.md",
			"content_type": "text/markdown",
			"size_bytes": 128
		}
	]
}

Errors

Each failure carries a precise code in the response. A capability denial is returned as a tool result with isError: true, so the agent can read the code and self-correct; a server fault is a JSON-RPC protocol error.

Code	Cause	Delivered as
capability_denied	The credential lacks the Resources capability required for this read.	tool error (isError)
internal_error	An unexpected error occurred.	protocol error (internal_error)

Notes

• The list mirrors what you can see over MCP — the same resources a client would see natively.
• To read a resource's content, pass its uri to get_resource; to search a large text resource without reading all of it, use grep_resource.
• Listing counts as one tool call against your plan's tool-invocation allowance.