Connecteam MCP Server and API by Cotlet

Copy previous week in Connecteam

connecteam_copy_previous_week

Read-onlyIdempotent

Copy previous week in the user's own Connecteam account from ChatGPT, Claude or any AI agent. Returns how to do it in Connecteam step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Connecteam Cloud Browser. Connecteam's official API: Connecteam has a REST API with read and write endpoints, but only on the Expert plan or higher, and its official MCP server only looks up API endpoints and cannot act on your account (checked 20 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": "connecteam_copy_previous_week"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it adds that the tool 'opens nothing by itself' and that the result is instructional rather than an executed change, which is exactly the behavior an agent needs to know to avoid double-acting. The extra note on Connecteam's REST API and official MCP server is contextual but not behavioral.

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 instruction and the follow-up tool guidance are front-loaded and useful, but the trailing sentence about Connecteam's REST API plans and its official MCP server is tangential, includes a dated verification claim, and dilutes the message.

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?

For a parameterless guidance tool with annotations covering safety and no output schema, the description covers what it returns and what the agent should do next. The API/MCP aside is not needed, but nothing essential is missing.

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 and 100% schema coverage, so the baseline is 4; there is nothing parameter-related left to explain and the description correctly implies no inputs are needed.

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 states a specific resource and action (copy previous week in Connecteam) and immediately clarifies the actual output: step-by-step instructions rather than an executed action. The verb is slightly misleading against the tool name, but the correction is explicit and distinguishes it from the cotlet_browser_* tools that perform the work.

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?

It clearly sequences usage: call this first to get the steps, then execute them with the cotlet_browser_* tools in the user's Connecteam Cloud Browser. It gives no explicit when-not-to-use guidance or prerequisites, so it falls short of a 5.

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

All Connecteam MCP Server and API by Cotlet tools Inspect

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

Need Help?