Skip to main content
Glama

List Cache Tasks

cache_task_list
Read-onlyIdempotent

List background cache tasks filtered by account and status to monitor queued, running, completed, or failed operations.

Instructions

📖 List background cache tasks (read-only, safe for unsupervised use)

Retrieve a list of background cache tasks, optionally filtered by account and status.

Args: account_id: Optional account ID to filter tasks (None = all accounts). status: Optional status filter (queued, running, completed, failed). limit: Maximum number of tasks to return (default: 50).

Returns: List of task dictionaries, each containing: - task_id: Task identifier - status: Current status - operation: Operation type - account_id: Associated account - priority: Task priority (1=highest, 10=lowest) - created_at: Creation timestamp - updated_at: Last update timestamp - retry_count: Number of retries

Example: # List all tasks for a specific account tasks = cache_task_list(account_id="user@example.com")

# List only failed tasks
failed = cache_task_list(status="failed")

# List recent queued tasks
queued = cache_task_list(status="queued", limit=10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNo
statusNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds 'read-only, safe for unsupervised use' and fully documents the return format (list of task dictionaries with fields), providing useful context beyond annotations. No contradictions.

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?

Well-structured with an initial summary line, then Args, Returns, and Examples sections. Every sentence adds value, no fluff or repetition. Front-loaded with key information.

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?

Even with an output schema, the description details return fields. Covers purpose, safety, parameters, output, and examples. Complete for a read-only listing tool.

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

Parameters5/5

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

Schema description coverage is 0%, but the description thoroughly explains each parameter (account_id, status, limit) with purpose, types, and defaults, plus examples. Fully compensates for missing schema 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?

Clearly states 'List background cache tasks' with verb and resource, and adds 'read-only, safe for unsupervised use' to distinguish it from mutation tools. Siblings like cache_invalidate are clearly different.

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?

Implies usage by detailing filtering options and providing examples, but does not explicitly compare to alternatives like cache_task_get_status. No 'when not to use' guidance.

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/robin-collins/m365-mcp'

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