Scribe Mail

List assets

list_assets

Read-onlyIdempotent

List the workspace's asset library (logos, banners, profile pictures), newest first. Each has its id, a downloadable file URL, its role, in_use (a signature or the workspace picture references it) and signature_template_count. Use it to reuse an image: put an asset's id in an image block's assetUuid (see get_content_schema) rather than uploading a duplicate with create_asset. Also use it to find the id for update_asset or delete_asset, and check in_use first, since delete_asset only soft-deletes an asset in use. Deleted assets are excluded and there is no filter by role, so page through and match role or name. Read-only; needs the assets:read scope. Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses the required assets:read scope, that deleted assets are excluded, that delete_asset only soft-deletes an asset in use, the sort order (newest first), and pagination behavior including the truncated flag. This is substantial behavioral context the annotations alone don't cover.

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

Conciseness4/5

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

The description is relatively long but front-loaded with the core purpose, then layers usage and pagination details, and every sentence earns its place. It is dense but not padded, with only minor over-packing of sibling-related details.

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

Completeness5/5

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

An output schema exists, so return-value explanation is not required, and the description still covers scope, filtering limits, sort order, pagination, and sibling routing. Nothing an agent needs to call the tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents the parameters, but the description adds real meaning: it ties auto_paginate to max_pages ('fetch up to max_pages') and states the default/max page size (50/100). This clarifies how the pagination parameters interact, going beyond the per-field descriptions.

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

Purpose5/5

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

The description gives a precise verb+resource ('List the workspace's asset library') and enumerates the resource types (logos, banners, profile pictures) and returned fields. It clearly separates this from create_asset, update_asset, and delete_asset, which are named as distinct operations.

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

Usage Guidelines5/5

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

Explicit when-to-use guidance: reuse an image by putting the asset's id in an image block's assetUuid rather than uploading a duplicate with create_asset, and use it to find the id for update_asset/delete_asset. It also names the condition to check in_use first, and discloses the no-filter-by-role constraint with the workaround (page and match role or name).

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

All Scribe Mail 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.