Skip to main content
Glama

list_projects

Retrieve projects from a Clockify workspace using filters like name, archived status, billable flag, client, or user. Supports pagination and can fetch all pages automatically.

Instructions

List projects on the workspace with optional filters (paginated). fetch_all=True follows pagination and returns every page concatenated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idNo
nameNo
strict_name_searchNo
archivedNo
billableNo
clientsNo
usersNo
is_templateNo
hydratedNo
sort_columnNo
sort_orderNo
pageNo
page_sizeNo
fetch_allNo
Behavior3/5

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

With no annotations, the description discloses pagination and fetch_all behavior but omits other traits like authentication needs or rate limits.

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, concise and front-loaded, with no unnecessary words.

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?

With 14 parameters and no output schema, the description is too brief, omitting details on filtering, sorting, and return format.

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

Parameters1/5

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

Schema coverage is 0%, yet the description only mentions 'optional filters' and fetch_all, failing to explain the other 12 parameters.

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

Purpose4/5

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

The description clearly states it lists projects with optional filters and pagination, but does not differentiate from sibling tools like list_tasks or list_clients.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions.

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/tracegazer/clockify-mcp'

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