Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_update_time_entry

Modify existing time entries in Harvest by updating project, task, date, hours, or notes to maintain accurate time tracking records.

Instructions

Update an existing time entry. Use about {"tool": "harvest_update_time_entry"} for detailed parameters and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTime entry ID
project_idNoProject ID
task_idNoTask ID
spent_dateNoDate of the entry (YYYY-MM-DD)
hoursNoHours worked
notesNoNotes for the time entry

Implementation Reference

  • Core implementation of the tool: sends PATCH request to Harvest API /time_entries/{id} with update data.
    async updateTimeEntry(id: string, data: any) {
      return this.makeRequest(`/time_entries/${id}`, {
        method: 'PATCH',
        body: JSON.stringify(data),
      });
    }
  • MCP CallToolRequestHandler switch case that extracts parameters and calls the HarvestClient.updateTimeEntry method.
    case 'harvest_update_time_entry':
      const { id, ...updateData } = typedArgs;
      const updatedTimeEntry = await harvestClient.updateTimeEntry(id as string, updateData);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(updatedTimeEntry, null, 2),
          },
        ],
      };
  • Tool definition including name, description, and inputSchema used for MCP tool listing and validation.
    {
      name: 'harvest_update_time_entry',
      description: 'Update an existing time entry. Use about {"tool": "harvest_update_time_entry"} for detailed parameters and examples.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Time entry ID' },
          project_id: { type: 'string', description: 'Project ID' },
          task_id: { type: 'string', description: 'Task ID' },
          spent_date: { type: 'string', description: 'Date of the entry (YYYY-MM-DD)' },
          hours: { type: 'number', description: 'Hours worked' },
          notes: { type: 'string', description: 'Notes for the time entry' }
        },
        required: ['id']
      }
    },
  • Detailed documentation and usage examples for the tool, provided via the 'about' tool.
          'harvest_update_time_entry': `# harvest_update_time_entry
    
    Updates an existing time entry with new information.
    
    ## Purpose
    Modify any aspect of an existing time entry including hours, notes, project, task, or date.
    
    ## Parameters
    - \`id\` (string, required): The time entry ID to update
    - \`project_id\` (string, optional): Change to different project
    - \`task_id\` (string, optional): Change to different task  
    - \`spent_date\` (string, optional): Change date (YYYY-MM-DD)
    - \`hours\` (number, optional): Update hours worked
    - \`notes\` (string, optional): Update notes/description
    
    ## Example Usage
    
    **Update hours and notes:**
    \`\`\`json
    {
      "tool": "harvest_update_time_entry",
      "id": "98765",
      "hours": 3.25,
      "notes": "Completed API integration and testing"
    }
    \`\`\`
    
    **Move entry to different project/task:**
    \`\`\`json
    {
      "tool": "harvest_update_time_entry",
      "id": "98765",
      "project_id": "54321",
      "task_id": "09876",
      "notes": "Moved to correct project"
    }
    \`\`\`
    
    **Change date:**
    \`\`\`json
    {
      "tool": "harvest_update_time_entry",
      "id": "98765", 
      "spent_date": "2024-01-19"
    }
    \`\`\`
    
    ## Response Format
    Returns the updated time entry object with all current values.
    
    ## Notes
    - Cannot update a running timer's hours (stop timer first)
    - Only provide parameters you want to change
    - Use harvest_list_time_entries to find entry IDs`,
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. It states this is an update operation, implying mutation, but doesn't disclose behavioral traits like permission requirements, whether changes are reversible, rate limits, or what happens to unspecified fields. The reference to 'about' for details doesn't add meaningful behavioral context.

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

Conciseness2/5

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

The description is two sentences, but the second sentence ('Use about...') is redundant and doesn't add value, as it merely points to another tool without providing useful information. This wastes space and reduces effectiveness, making it under-specified rather than concise.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like what the tool returns, error conditions, or how it interacts with sibling tools. The reference to 'about' doesn't compensate for these gaps, making it inadequate for the complexity.

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 fully documents all 6 parameters. The description adds no additional meaning beyond what's in the schema, such as explaining relationships between parameters or providing examples. This meets the baseline of 3 when schema coverage is high.

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 'Update an existing time entry' which provides a clear verb ('Update') and resource ('time entry'), but it doesn't differentiate from sibling tools like harvest_create_time_entry or harvest_delete_time_entry beyond the basic action. It's not tautological but lacks specific distinction from 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 provides no guidance on when to use this tool versus alternatives like harvest_create_time_entry or harvest_delete_time_entry. It only references using 'about' for parameters, which doesn't address usage context or prerequisites. No explicit when/when-not statements are included.

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