CoachingPortal by Cotlet

Manage landing page in CoachingPortal

coachingportal_manage_landing_page

Read-onlyIdempotent

Manage landing page in the user's own CoachingPortal account from ChatGPT, Claude or any AI agent. Returns how to do it in CoachingPortal step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser. CoachingPortal's official API: CoachingPortal publishes no public API.

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": "coachingportal_manage_landing_page"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them ("opens nothing by itself"). It adds useful context that no public CoachingPortal API exists, so browser automation is the only path, but it says nothing about rate limits, permissions, or how the returned instructions are shaped beyond mentioning screens/buttons/fields.

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 workflow information is front-loaded and useful, but the closing line "CoachingPortal's official API: CoachingPortal publishes no public API." is repetitive and awkwardly framed. The opening clause about ChatGPT/Claude/any AI agent is also padding that does not help an agent decide or call.

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 zero-parameter, no-output-schema guidance tool, the description covers what is returned (step-by-step screens, buttons, fields), what it does not do, and which tools to use next. That is nearly everything an agent needs, with only the absence of any output format detail as a minor gap.

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?

The tool takes zero parameters, so the schema carries no semantics to compensate for; the baseline applies. The description also makes clear the scope is implicitly the user's own account, which is the only meaningful input dimension left undefined.

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 names a specific resource (landing page in the user's own CoachingPortal account) but uses the vague verb "manage", which spans create/update/delete. It compensates by clarifying the actual operation: it returns step-by-step instructions (screens, buttons, fields) rather than performing the action, which lets an agent distinguish it from browser tools that do 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 describes the workflow explicitly: call this to get the steps, then perform them with the cotlet_browser_* tools in the Cloud Browser. It also sets clear expectations by stating it "opens nothing by itself". It stops short of naming when NOT to use it or naming a specific sibling alternative.

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

All CoachingPortal 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?