Paired Plus by Cotlet

Manage product in Paired Plus

paired_plus_manage_product

Read-onlyIdempotent

Manage product in the user's own Paired Plus account from ChatGPT, Claude or any AI agent. Returns how to do it in Paired Plus step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser. Paired Plus's official API: The ProSolutions Paired host publishes API help, but no self-serve API key or onboarding guide was found.

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

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

Behavior4/5

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

Beyond the readOnlyHint=true annotation, the description explicitly states that the tool 'opens nothing by itself' and only returns instructions, which is important context for an agent tempted to treat 'Manage product' as a write operation. It also discloses the API-key/onboarding limitation, though it does not discuss authentication or rate limits for the actual browser execution step.

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 key workflow and no-side-effect statements are front-loaded and useful. However, phrases like 'from ChatGPT, Claude or any AI agent' are marketing filler, and the API help sentence is somewhat tangential, keeping the description from being maximally tight.

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, read-only guidance tool without an output schema, the description explains what is returned (step-by-step screens, buttons, fields) and what to do next (use cotlet_browser_* tools). The only gap is that it does not define the scope of 'product management' actions it can guide, which may matter for an agent choosing between this and more specific product-related siblings.

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 has zero input parameters, so there is no parameter semantics burden. The schema is empty and the description appropriately does not invent parameter meanings.

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 says 'Manage product' but does not specify which product operations (create, update, pricing, inventory) are covered, leaving the verb vague. It does clarify that the tool returns step-by-step instructions rather than performing the action, but it does not distinguish this general product-management guidance from more specific siblings like paired_plus_create_product_kit or paired_plus_configure_product_purchase_reminder.

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 gives a clear usage sequence: call this to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools. It does not say when to use this versus other paired_plus_* siblings or provide exclusions, but the execution handoff is explicit.

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

All Paired Plus 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?