Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_list_tasks

Retrieve and filter tasks from Harvest time tracking with options for active status, pagination, and results per page.

Instructions

List all tasks with filtering options. Use about {"tool": "harvest_list_tasks"} for detailed parameters and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
is_activeNoFilter by active status
pageNoPage number
per_pageNoResults per page (max 100)

Implementation Reference

  • src/tools.ts:130-141 (registration)
    Tool registration in the tools array, including name, description, and input schema definition.
    {
      name: 'harvest_list_tasks',
      description: 'List all tasks with filtering options. Use about {"tool": "harvest_list_tasks"} for detailed parameters and examples.',
      inputSchema: {
        type: 'object',
        properties: {
          is_active: { type: 'boolean', description: 'Filter by active status' },
          page: { type: 'number', description: 'Page number' },
          per_page: { type: 'number', description: 'Results per page (max 100)' }
        }
      }
    },
  • MCP server request handler for the tool, which delegates to HarvestClient.getTasks() and formats the response as JSON text.
    case 'harvest_list_tasks':
      const tasks = await harvestClient.getTasks(typedArgs);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(tasks, null, 2),
          },
        ],
      };
  • Core implementation method in HarvestClient that makes the API request to /tasks endpoint with query parameters.
    async getTasks(options?: any) {
      const queryString = this.buildQueryString(options);
      return this.makeRequest(`/tasks${queryString}`);
    }
  • Detailed documentation and usage examples for the harvest_list_tasks tool provided by the about handler.
          'harvest_list_tasks': `# harvest_list_tasks
    
    Lists all tasks available in your Harvest account.
    
    ## Purpose
    Retrieve task information needed for creating time entries and understanding work categories.
    
    ## Parameters
    - \`is_active\` (boolean, optional): Filter by active/inactive status
    - \`page\` (number, optional): Page number for pagination
    - \`per_page\` (number, optional): Results per page, max 100
    
    ## Example Usage
    
    **List all active tasks:**
    \`\`\`json
    {
      "tool": "harvest_list_tasks",
      "is_active": true
    }
    \`\`\`
    
    **List all tasks with pagination:**
    \`\`\`json
    {
      "tool": "harvest_list_tasks",
      "page": 1,
      "per_page": 50
    }
    \`\`\`
    
    ## Response Format
    Returns an object with:
    - \`tasks\`: Array of task objects
    - Pagination information
    
    Each task includes: id, name, billable_by_default, is_active, is_default, hourly_rate, created_at, updated_at.
    
    ## Important Notes
    - Tasks are global but must be assigned to projects
    - Use harvest_list_task_assignments to see which tasks are available for a specific project
    - Not all tasks are valid for all projects`,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'filtering options' and pagination (implied by 'page' and 'per_page' in schema), but does not cover critical aspects like authentication requirements, rate limits, error handling, or return format. For a list tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences: one stating the purpose and another directing to another tool for details. It is front-loaded with the main function, but the second sentence is somewhat redundant since parameters are already in the schema. Overall, it is efficient with minimal waste, though the reference to 'about' could be streamlined.

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?

Given no annotations, no output schema, and 3 parameters with full schema coverage, the description is incomplete. It lacks details on behavioral traits (e.g., pagination behavior, error responses) and does not explain return values or usage context. For a tool with filtering and pagination, more guidance is needed to ensure the agent can use it effectively.

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 description coverage is 100%, with clear descriptions for 'is_active,' 'page,' and 'per_page.' The description adds no additional parameter semantics beyond what the schema provides, such as default values or usage examples. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately documents parameters without extra help from the description.

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

Purpose3/5

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

The description states the tool 'List all tasks with filtering options,' which provides a clear verb ('List') and resource ('tasks') with scope ('all'). However, it does not differentiate from sibling tools like 'harvest_list_task_assignments' or 'harvest_list_time_entries,' making it somewhat vague in comparison. The purpose is understandable but lacks specificity relative to alternatives.

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?

The description includes a directive to 'Use about {"tool": "harvest_list_tasks"} for detailed parameters and examples,' which implies usage guidance but does not explicitly state when to use this tool versus alternatives like 'harvest_list_task_assignments.' No context, exclusions, or prerequisites are provided, leaving the agent with minimal guidance on tool selection.

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/standardbeagle/harvest-mcp'

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