api

List Collections

collection.list

Read-onlyIdempotent

List all document collections owned by your API key. Free — no credits consumed. Use before collection.search or collection.ask when you need the collection ID. Supports pagination with limit and offset. Returns: { collections: [{ id, name, created_at }] } Example prompts:

"List all my document collections."
"Show me the collections I have created."
"What collections do I own? List them."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max collections to return (default 50, max 100). Example: 20
`offset`	No	Pagination offset (default 0). Example: 0

Output Schema

TableJSON Schema

Name	Required	Description	Default
`collections`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

Adds behavioral context beyond annotations: states it is free (no credits consumed), supports pagination, and returns a specific structure. Annotations already indicate read-only and idempotent, so description complements them well.

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?

Well-structured with main purpose first, followed by usage guidance, return format, and examples. Slightly lengthy but all content is relevant and earns its place.

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?

Complete for a simple list tool: covers purpose, usage context, parameters, return value, and examples. No gaps given the low complexity and full schema/output schema.

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 fully documents limit and offset. The description adds value by explaining pagination context and showing example output, going beyond just repeating schema details.

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?

Clearly states 'List all document collections owned by your API key' with specific verb and resource. Distinguishes from sibling tools like collection.search and collection.ask by mentioning it is used to get collection IDs. Also notes it is free and uses no credits.

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?

Explicitly advises using this tool before collection.search or collection.ask when needing the collection ID. Provides example prompts that illustrate common use cases.

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

All api tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose, with no overlap. The category prefixes (account, bundle, collection, document, job, receipt, url) and specific action names (get, notarize, verify, create, list, etc.) ensure that an agent can unambiguously select the correct tool for any task.

Naming Consistency5/5

All tools follow a consistent category.action or category.action_noun pattern using snake_case (e.g., bundle.get, collection.add_document, url.translate). No mixed conventions or irregular names, making the pattern predictable and easy to learn.

Tool Count4/5

With 22 tools, the set is somewhat large but each tool addresses a distinct need within a broad domain (evidence management, document AI, collections, URL processing, job tracking, receipts). The count is slightly above the typical well-scoped range but still reasonable given the scope.

Completeness2/5

The tool surface has notable gaps: there is no tool to create or delete an evidence bundle, nor to update collections or bundles. The core workflow of creating a bundle from a document is missing, and the lifecycle is incomplete, which would likely cause agent failures in typical use cases.

Resources

Need Help?