Skip to main content
Glama

List documents and document groups

list_documents
Read-onlyIdempotent

Retrieve a unified list of documents and document groups filtered by status, expiration, folder, sorted by date or name, with pagination.

Instructions

Get simplified list of documents and document groups with basic information. Returns both documents and document groups in a unified format. Use this tool to fetch lists of documents by status, e.g. documents waiting for your signature (waiting-for-me) or expired documents (expired_filter=expired).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter by document group status (optional). Available values: signed, pending, waiting-for-me, waiting-for-others, unsent.
sortbyNoSort by created date, updated date, or document name (optional). Available values: updated, created, document-name.
orderNoOrder of sorting (optional, can be used only with sortby). Available values: asc, desc.
folder_idNoFilter by folder ID (optional)
expired_filterNoFilter by invite expiredness (optional, default: all). Available values: all, expired, not-expired.all
limitNoMaximum number of items to return (1-100, default 50)
offsetNoNumber of items to skip for pagination (default 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_groupsYes
document_group_total_countYesTotal number of document groups across all pages
offsetNoNumber of items skipped
limitNoMaximum number of items in this page
has_moreNoWhether more items exist beyond this page
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about the unified format and examples. It does not contradict annotations and provides some extra behavioral context, though pagination details are not mentioned.

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?

The description consists of two sentences that front-load the purpose and provide a usage example. Every sentence earns its place with no unnecessary words.

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?

With output schema present and all parameters documented, the description covers the main purpose and gives relevant examples. It could briefly mention the unified format nature or pagination, but overall it is sufficient for an AI agent to understand when and how to use the tool.

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% with descriptions for all 7 parameters. The description adds examples (e.g., waiting-for-me, expired) but does not significantly add meaning beyond the schema. Baseline score of 3 is appropriate.

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 clearly states the verb 'Get', the resource 'list of documents and document groups', and specifies it returns basic information in a unified format. It distinguishes from sibling tools by giving filtering examples, showing it is a read-only listing tool.

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

Usage Guidelines4/5

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

The description provides specific use cases like finding documents waiting for your signature or expired documents. However, it does not explicitly mention when not to use this tool or offer alternatives such as get_document for individual documents or list_all_templates for templates.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signnow/sn-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server