Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_list_task_assignments

Retrieve assigned tasks for a specific project in Harvest, with options to filter by active status and paginate results.

Instructions

List task assignments for a project. Use about {"tool": "harvest_list_task_assignments"} for detailed workflow and examples.

Input Schema

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

Implementation Reference

  • Main handler for the tool in the MCP server switch statement. Calls the HarvestClient method and returns formatted JSON response.
    case 'harvest_list_task_assignments':
      const taskAssignments = await harvestClient.getTaskAssignments(typedArgs.project_id as string, typedArgs);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(taskAssignments, null, 2),
          },
        ],
      };
  • Core implementation that performs the HTTP request to the Harvest API endpoint for task assignments of a project.
    async getTaskAssignments(projectId: string, options?: any) {
      const queryString = this.buildQueryString(options);
      return this.makeRequest(`/projects/${projectId}/task_assignments${queryString}`);
    }
  • Input schema definition and tool metadata used for validation and listing.
    {
      name: 'harvest_list_task_assignments',
      description: 'List task assignments for a project. Use about {"tool": "harvest_list_task_assignments"} for detailed workflow and examples.',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          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)' }
        },
        required: ['project_id']
      }
    }
  • src/index.ts:69-73 (registration)
    Registers the tools list handler which includes this tool via imported tools array from tools.ts.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: tools,
      };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, it doesn't specify authentication requirements, rate limits, pagination behavior (beyond what parameters suggest), error conditions, or what the output contains. The reference to 'about' for details is insufficient for immediate understanding.

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

Conciseness3/5

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

The description is brief but inefficiently structured. The first sentence is functional but basic. The second sentence about using 'about' adds questionable value as it's a meta-reference that doesn't help the agent understand the tool itself. While not verbose, the content doesn't maximize its limited word count.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'task assignments' are in this context, what the output format looks like, or how results are structured. The reference to another tool for details doesn't compensate for these gaps in the primary description.

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%, so the schema already documents all four parameters adequately. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify edge cases. This meets the baseline for high schema coverage.

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 'List task assignments for a project', which clearly indicates the verb (list) and resource (task assignments) with a scope (for a project). However, it doesn't differentiate from sibling tools like 'harvest_list_project_assignments' or 'harvest_list_tasks', leaving ambiguity about what specifically distinguishes this tool from related listing operations.

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 provides no guidance on when to use this tool versus alternatives. It mentions using 'about' for detailed workflow and examples, but this is a meta-reference rather than practical usage advice. There's no indication of prerequisites, when-not-to-use scenarios, or comparisons with sibling tools like 'harvest_list_project_assignments' or 'harvest_list_tasks'.

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