Peerspace MCP Server and API by Cotlet

Update listing pricing in Peerspace

peerspace_update_listing_pricing

Read-onlyIdempotent

Update listing pricing in the user's own Peerspace account from ChatGPT, Claude or any AI agent. Returns how to do it in Peerspace step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Peerspace Cloud Browser. Peerspace's official API: Peerspace has no public API, developer portal or webhooks for hosts (checked 11 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": "peerspace_update_listing_pricing"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself' plus a description of what is returned (screens, buttons, fields). It also adds the useful constraint that Peerspace has no public API, developer portal, or webhooks as of 11 Oct 2026, explaining why the browser-tool path exists. It stops short of covering session/auth prerequisites or what happens if the user is not logged in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences that are front-loaded with the purpose and the critical caveat. The 'from ChatGPT, Claude or any AI agent' phrase is marketing filler that does not help an agent decide or call, and the tool name slightly overpromises an update that the body then corrects.

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

Completeness5/5

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

For a parameterless instruction-returning tool with no output schema and read-only annotations, the description covers everything needed: what it returns, that it performs no action, which tools to use next, and why no direct API route exists. Nothing an agent needs in order to call it correctly 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?

The tool takes zero parameters, so the baseline is 4. The description adds no parameter detail, but none is needed given the empty schema with additionalProperties=false.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description states a specific action and resource ('Update listing pricing in the user's own Peerspace account') and immediately clarifies the actual mechanism: 'Returns how to do it in Peerspace step by step (screens, buttons, fields) and opens nothing by itself.' This disambiguates it from a real mutation and 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 Guidelines5/5

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

It prescribes the exact workflow: call this tool to get step-by-step instructions, then execute with the cotlet_browser_* tools in the user's Peerspace Cloud Browser. Saying 'opens nothing by itself' preempts the most likely misuse (expecting this tool to make the change), which functions as an explicit when-not condition.

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

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