Skip to main content
Glama
jais2402
by jais2402

List Everhour projects

everhour_list_projects
Read-onlyIdempotent

Search or list Everhour projects with optional filters by platform, name, or archived status. Retrieve project IDs to use in other tools and confirm sync from Asana.

Instructions

List or search Everhour projects, optionally filtered by source platform (e.g. Asana).

Useful for:

  • Discovering project IDs needed by other tools

  • Confirming an Asana project has been synced into Everhour

  • Browsing what work the user has access to

Args:

  • query (string, optional): Filter by name substring

  • platform ('asana' | 'trello' | 'jira' | 'github' | 'basecamp' | 'everhour', optional)

  • archived (boolean, optional): Include archived projects

  • limit, offset: Pagination (default limit=25, max 250)

  • response_format ('markdown' | 'json'): Output format (default 'markdown')

Returns: JSON shape: { "total": number, "count": number, "offset": number, "items": [{ "id": "as:...", "name": string, "platform": string, "status": string, "client"?: { "name": string }, ... }], "has_more": boolean, "next_offset"?: number }

Examples:

  • "List my Asana projects in Everhour" → platform='asana'

  • "Find the 'Lynx Dashboard' project" → query='Lynx Dashboard'

Error Handling:

  • 401 → check EVERHOUR_API_KEY

  • 429 → rate-limited, wait and retry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (1-250, default 25)
queryNoOptional search string. Filters projects by name (Everhour /projects?query=).
offsetNoNumber of results to skip for pagination (default 0)
archivedNoIf true, include archived projects.
platformNoFilter by source platform. Use 'asana' to list only Asana-synced projects.
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds error handling details (401, 429) and the return shape, providing transparency 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?

The description is well-structured with sections (use cases, args, returns, examples, error handling). It front-loads the main purpose and every sentence adds value. No unnecessary text.

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?

All relevant aspects are covered: parameter details, return shape, pagination, error handling, and example scenarios. With no output schema and 6 optional parameters, the description fully equips an AI agent to use this tool correctly.

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 coverage is 100% with descriptions for all 6 parameters. The description further clarifies query as substring, platform values, archived flag, pagination defaults, and response_format. Examples reinforce parameter usage.

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 title and description clearly state the tool lists or searches Everhour projects with optional platform filtering. It is distinct from sibling tools like everhour_get_project (single project) or everhour_search_tasks (tasks).

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 lists specific use cases (discovering project IDs, confirming sync, browsing) and includes examples. However, it does not explicitly contrast with alternative tools (e.g., everhour_get_project for a single project by ID), which could be helpful.

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/jais2402/ever-hour-mcp-for-jais'

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