Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_list_users

Retrieve and filter user accounts in Harvest to manage team access and permissions for time tracking and project management.

Instructions

List all users in the account with filtering. Use about {"tool": "harvest_list_users"} 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 handler case in the MCP tool execution switch statement that invokes harvestClient.getUsers with the provided arguments and formats the response as MCP content.
    case 'harvest_list_users':
      const users = await harvestClient.getUsers(typedArgs);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(users, null, 2),
          },
        ],
      };
  • Defines the tool metadata including name, description, and input schema for parameter validation.
    {
      name: 'harvest_list_users',
      description: 'List all users in the account with filtering. Use about {"tool": "harvest_list_users"} 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:68-73 (registration)
    Registers the tools list (including harvest_list_users) with the MCP server for tool discovery via ListToolsRequest.
    // Handle tool listing
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: tools,
      };
    });
  • The supporting method in HarvestClient that performs the actual API request to /users endpoint with query parameters.
    async getUsers(options?: any) {
      const queryString = this.buildQueryString(options);
      return this.makeRequest(`/users${queryString}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'filtering' and pagination parameters, but doesn't disclose critical behavioral traits like whether this is a read-only operation (implied by 'List'), rate limits, authentication requirements, or what happens with invalid parameters. The description is insufficient for a tool with no annotation coverage.

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 contains redundant elements. The first sentence is useful, but the second sentence about 'about' tool is unnecessary and doesn't add value for an AI agent. The structure could be improved by front-loading more specific information about filtering scope.

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 and no output schema, the description is incomplete. It doesn't explain what the tool returns (user objects, pagination metadata), error conditions, or important constraints like the 'max 100' in the schema. For a list tool with filtering and pagination, more context is needed about the response format and behavior.

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 three parameters. The description adds minimal value by mentioning 'filtering' generically, but doesn't provide additional context beyond what's in the schema descriptions. 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.

Purpose4/5

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

The description clearly states the verb 'List' and resource 'users in the account', making the purpose understandable. It distinguishes from siblings like 'harvest_get_current_user' (single user) and 'harvest_list_clients' (different resource). However, it doesn't specify what 'filtering' entails beyond the schema parameters.

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_get_current_user' for a single user or other list tools for different resources. It mentions filtering but doesn't explain when filtering is appropriate versus using other tools.

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