Skip to main content
Glama

activities_list_all_auto

Automatically retrieve all activities across every page without manual pagination. Filter results by user, type, date range, or completion status.

Instructions

Automatically fetch all activities across all pages. Use this when you need complete data without manual pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoFilter by user ID
typeNoActivity type
doneNoFilter by done status (true for done, false for not done)
start_dateNoStart date filter (YYYY-MM-DD)
end_dateNoEnd date filter (YYYY-MM-DD)
max_itemsNoMaximum number of items to fetch
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It mentions automatic pagination but fails to discuss rate limits, potential large data loads, or side effects. Insufficient for a tool that may fetch many records.

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?

Two sentences, front-loaded with actionable verb, no wasted words. Structured effectively for quick understanding.

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

Completeness2/5

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

Despite good schema coverage, missing output schema and annotations. Description does not explain return format, pagination behavior, or max_items impact. Incomplete for a tool that could return large datasets.

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 covers 100% of parameters with descriptions. Description adds no additional meaning beyond the schema, so baseline 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?

Description clearly states 'fetch all activities across all pages' with a specific verb and resource. It distinguishes itself from siblings like activities_list by handling automatic pagination.

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?

Explicitly advises use when 'complete data without manual pagination' is needed, implying context. Lacks explicit when-not-to-use or alternative names, but sibling names provide differentiation.

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/iamsamuelfraga/mcp-pipedrive'

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