Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_restart_timer

Restart a stopped time entry timer in Harvest to resume tracking work hours for accurate time management.

Instructions

Restart a stopped time entry timer. Use about {"tool": "harvest_restart_timer"} for detailed workflow and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTime entry ID

Implementation Reference

  • Core handler function that implements the Harvest API call to restart a time entry timer via PATCH /time_entries/{id}/restart.
    async restartTimer(id: string) {
      return this.makeRequest(`/time_entries/${id}/restart`, {
        method: 'PATCH',
      });
    }
  • MCP server request handler case that dispatches harvest_restart_timer calls to the HarvestClient.restartTimer method.
    case 'harvest_restart_timer':
      const restartedTimer = await harvestClient.restartTimer(typedArgs.id as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(restartedTimer, null, 2),
          },
        ],
      };
  • src/tools.ts:62-72 (registration)
    Tool registration in the tools array, including name, description, and input schema requiring 'id' parameter.
    {
      name: 'harvest_restart_timer',
      description: 'Restart a stopped time entry timer. Use about {"tool": "harvest_restart_timer"} for detailed workflow and examples.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Time entry ID' }
        },
        required: ['id']
      }
    },
  • Input schema definition specifying the required 'id' parameter of type string for the harvest_restart_timer tool.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Time entry ID' }
      },
      required: ['id']
    }
  • Detailed documentation and usage examples for the harvest_restart_timer tool provided in the getAboutInfo method.
          'harvest_restart_timer': `# harvest_restart_timer
    
    Restarts a stopped time entry timer to resume time tracking.
    
    ## Purpose
    Resume timing on a previously stopped time entry, setting is_running to true and timer_started_at to current time.
    
    ## Parameters
    - \`id\` (string, required): The time entry ID to restart
    
    ## Example Usage
    
    **Restart a stopped timer:**
    \`\`\`json
    {
      "tool": "harvest_restart_timer",
      "id": "98765"
    }
    \`\`\`
    
    ## Response Format
    Returns the updated time entry with:
    - \`is_running\`: true
    - \`timer_started_at\`: Current timestamp
    - \`hours\`: Previous accumulated hours
    - All other time entry properties
    
    ## Requirements
    - Time entry must exist
    - Timer must not already be running
    - Only one timer can run at a time per user
    
    ## Workflow
    1. Find stopped entry: harvest_list_time_entries
    2. Restart timer: harvest_restart_timer  
    3. Work on the task
    4. Stop when done: harvest_stop_timer
    
    ## Error Conditions
    - Entry not found: Invalid ID
    - Timer already running: Cannot restart running timer
    - Another timer running: Stop other timer first`,
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 states the action ('Restart a stopped time entry timer') which implies a mutation operation, but doesn't disclose critical behavioral traits such as required permissions, whether it affects billing or reporting, error conditions (e.g., if the timer isn't stopped), or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately concise with two sentences. The first sentence clearly states the tool's purpose, and the second provides a reference for more details. There's no unnecessary verbosity, and the information is front-loaded, though the second sentence could be more integrated into the main description.

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 the complexity of a mutation tool (restarting a timer) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error handling, or response format, and relies on external references ('about') for details. For a tool that modifies state, this lack of context is inadequate for safe and effective use by an AI agent.

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?

The description adds no parameter semantics beyond what the input schema provides. The schema has 100% coverage with a clear description for the 'id' parameter ('Time entry ID'), so the baseline score is 3. The description doesn't explain what constitutes a valid time entry ID, how to obtain it, or any constraints, leaving all parameter documentation to the schema.

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 action ('Restart a stopped time entry timer') which is clear but somewhat vague. It specifies the resource type ('time entry timer') but doesn't differentiate from sibling tools like 'harvest_stop_timer' or 'harvest_update_time_entry' beyond the basic verb difference. The purpose is understandable but lacks specificity about what distinguishes this restart operation from other time entry modifications.

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 doesn't mention prerequisites (e.g., the timer must be stopped), exclusions, or comparisons to sibling tools like 'harvest_stop_timer' or 'harvest_update_time_entry'. The reference to 'about {"tool": "harvest_restart_timer"}' suggests external documentation but doesn't offer actionable usage context within the description itself.

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