Skip to main content
Glama
jais2402
by jais2402

Search Everhour tasks

everhour_search_tasks
Read-onlyIdempotent

Search Everhour tasks by name to find Asana-synced tasks. Optionally scope by project ID for targeted results.

Instructions

Search tasks in Everhour by name, optionally scoped to a project.

This is the primary way to find an Everhour task that mirrors an Asana ticket when you only know the ticket name. Asana-synced tasks appear with IDs like 'as:'.

Args:

  • query (string): Search string, 1-200 chars

  • project_id (string, optional): Scope search to this Everhour project ID

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

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

Returns: { "total": number, "count": number, "offset": number, "items": [{ "id": "as:...", "name": string, "url": string, "status"?: string, "projects"?: string[] }], "has_more": boolean, "next_offset"?: number }

Examples:

  • "Find Everhour task for 'Fix login bug'" → query='Fix login bug'

  • "Find all design review tasks in project as:120801..." → query='design review', project_id='as:120801...'

Error Handling:

  • 400 → query is empty

  • 429 → rate-limited

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (1-250, default 25)
queryYesSearch string. Matches task name and (for synced tasks) the source platform's task name. Examples: 'login bug', 'OPS-123'.
offsetNoNumber of results to skip for pagination (default 0)
project_idNoOptional Everhour project ID to scope the search (e.g. 'as:120801...').
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds behavioral details such as matching by name and source platform task name, return structure, error codes (400, 429), and pagination behavior. No contradiction with annotations.

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 concise and well-structured with clear sections (purpose, Args, Returns, Examples, Error Handling). Every sentence provides value, and the format is easy to parse. No redundancy.

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?

Given five parameters, full schema coverage, no output schema, the description provides comprehensive information: usage examples, return format, pagination details, and error handling. An agent has all necessary context to invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. The description adds meaningful context: query length constraints, project_id format (e.g., 'as:...'), pagination defaults and limits, and response_format options. Examples further clarify 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 description clearly states that the tool searches tasks by name with optional project scoping. It explicitly identifies itself as the primary way to find Asana-synced tasks when only the ticket name is known, distinguishing it from the sibling everhour_find_task_by_asana_id.

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 clear context ('primary way to find an Everhour task that mirrors an Asana ticket') and examples. However, it does not explicitly state when to avoid this tool or mention alternatives like everhour_find_task_by_asana_id for direct Asana ID lookup.

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