Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_list_clients

Retrieve and filter client information from Harvest time tracking system to manage business relationships and project organization.

Instructions

List all clients with filtering options. Use about {"tool": "harvest_list_clients"} 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

  • The main handler function that executes the tool logic: builds query parameters from input (is_active, page, per_page) and fetches clients list from Harvest API /clients endpoint.
    async getClients(options?: any) {
      const queryString = this.buildQueryString(options);
      return this.makeRequest(`/clients${queryString}`);
    }
  • Defines the tool's name, description, and input schema for validation (filters: is_active, page, per_page).
    {
      name: 'harvest_list_clients',
      description: 'List all clients with filtering options. Use about {"tool": "harvest_list_clients"} 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)' }
        }
      }
    },
  • src/index.ts:69-73 (registration)
    Registers all tools (including harvest_list_clients) for the MCP listTools request, providing schemas to clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: tools,
      };
    });
  • MCP server dispatch handler case that receives tool call, passes arguments to client.getClients(), and formats JSON response.
    case 'harvest_list_clients':
      const clients = await harvestClient.getClients(typedArgs);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(clients, null, 2),
          },
        ],
      };
  • Helper function used by getClients to construct URL query string from input parameters.
    private buildQueryString(params?: Record<string, any>): string {
      if (!params) return '';
      
      const queryParams = new URLSearchParams();
      Object.entries(params).forEach(([key, value]) => {
        if (value !== undefined && value !== null) {
          queryParams.append(key, String(value));
        }
      });
      
      const queryString = queryParams.toString();
      return queryString ? `?${queryString}` : '';
    }
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 via parameters, but fails to describe key behaviors such as authentication requirements, rate limits, error handling, or what the output looks like (e.g., list format). This is inadequate for a tool with multiple parameters and no output schema.

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 is redundant and adds no value—it merely references the tool itself for details, which is tautological. This wastes space and fails to front-load useful information, making it inefficient and poorly structured.

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 tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, output format, and usage context. For a list tool with filtering, more information is needed to guide effective use, making it insufficient 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 input schema fully documents the parameters (is_active, page, per_page). The description adds no additional meaning beyond implying filtering exists, which is already covered. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 clients with filtering options', which provides a clear verb ('List') and resource ('clients'). However, it doesn't distinguish this tool from sibling tools like 'harvest_list_projects' or 'harvest_list_users' beyond the resource type, making it somewhat vague in comparison. The purpose is understandable but lacks specific differentiation.

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 filtering options but doesn't specify contexts, prerequisites, or exclusions. For example, it doesn't clarify if this is for administrative tasks or general client lookup, leaving usage ambiguous.

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