Skip to main content
Glama
Sign In

PeoplePerHour MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Watch and unwatch projects in PeoplePerHour

peopleperhour_watch_and_unwatch_projects
Read-onlyIdempotent

Watch and unwatch projects in the user's own PeoplePerHour account from ChatGPT, Claude or any AI agent. Returns how to do it in PeoplePerHour step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's PeoplePerHour Cloud Browser. PeoplePerHour's official API: PeoplePerHour has no public API and no developer docs (checked 12 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "peopleperhour_watch_and_unwatch_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description is consistent with that while adding real value: it discloses that nothing is opened as a side effect, that the output is procedural guidance, and that execution requires the separate browser tool family. The note that PeoplePerHour has no public API explains why a guidance-based approach exists at all.

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 core disclosure (returns steps, opens nothing, execute via cotlet_browser_*) is well front-loaded, but words like 'from ChatGPT, Claude or any AI agent' are marketing filler and the trailing API sentence is awkwardly constructed ('PeoplePerHour's official API: PeoplePerHour has no public API...'), burying a useful fact in a malformed clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the job of explaining the return value, and it does so ('how to do it in PeoplePerHour step by step (screens, buttons, fields)'). Combined with the handoff to cotlet_browser_* tools, an agent has enough to act; only the absence of sibling routing against peopleperhour_list_watchlist keeps it short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is no parameter meaning to convey; baseline 4 applies. The description correctly implies no inputs are needed and points at the browser tools that will carry the actual arguments.

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?

Names a specific verb pair and resource (watch/unwatch projects) scoped to the user's own PeoplePerHour account, and immediately clarifies that it returns step-by-step instructions rather than performing the action. It is distinguishable from siblings like peopleperhour_list_watchlist, though that sibling is never named explicitly to contrast read-vs-write intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear workflow: call this to get screens/buttons/fields, then execute with cotlet_browser_* tools in the user's Cloud Browser. It lacks an explicit 'do not use this for X, use peopleperhour_list_watchlist instead' exclusion, so routing against siblings is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PeoplePerHour MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources