BotSpot: AI Trading, Backtests and Bots

Create or update an account or strategy publication

save_marketplace_publication

Destructive

Creates or updates a draft for exactly one explicit subject. Can set Marketplace presentation and default-deny capabilities, then optionally publish. To save your default positions, filled-trade and open-order sharing for first-time strategy publications, pass publishingDefaults alone: policy contains those three booleans, excludedNameContains contains case-insensitive literal strategy-name phrases whose default is private. No subjectKind or other publication fields in that operation. Defaults never republish a strategy or alter existing publications; explicit per-publication choices win. Read defaults and sharing history through my_marketplace_publications(action="list"). Set regenerateHeroImage=true to generate and upload fresh artwork through the website GPT Image 2.5 service (one paid generation, 5/day). Existing artwork stays until replacement succeeds. An account publication contains no strategies. A strategy publication contains only that strategy and an optional account performance projection.

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

Input Schema

Name	Required	Description
`tags`	No
`title`	No
`details`	No
`publish`	No	Publish after saving. Default false.
`accountId`	No
`allowClone`	No
`strategyId`	No
`description`	No
`subjectKind`	No
`assetClasses`	No
`allowCodeView`	No
`removeHeroImage`	No
`autoPublishTrades`	No	Explicit consent to automatically post future confirmed fills in Community. Requires filled-trade visibility.
`allowPositionsView`	No
`publishingDefaults`	No
`allowOpenOrdersView`	No
`regenerateHeroImage`	No	Regenerate and upload artwork using the same service as website Settings. Do not combine with removeHeroImage.
`allowPerformanceView`	No
`allowTradeReasonView`	No	Explicit consent to publish private trade explanations in Community.
`allowAccountValueView`	No	Show the dollar account value, cash, dollar history and position prices. New account shares turn this on by default.
`allowFilledTradesView`	No
`allowExactQuantitiesView`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

addedInput schema / properties / allowAccountValueView

Added value: +{
+  "description": "Show the dollar account value, cash, dollar history and position prices. New account shares turn this on by default.",
+  "type": "boolean"
+}

Changed2 schema fields changedNov 7, 2026

addedInput schema / properties / publishingDefaults

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "excludedNameContains": {
+      "items": {
+        "maxLength": 140,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 50,
+      "type": "array"
+    },
+    "policy": {
+      "additionalProperties": false,
+      "properties": {
+        "allowFilledTradesView": {
+          "type": "boolean"
+        },
+        "allowOpenOrdersView": {
+          "type": "boolean"
+        },
+        "allowPositionsView": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "allowPositionsView",
+        "allowFilledTradesView",
+        "allowOpenOrdersView"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "policy",
+    "excludedNameContains"
+  ],
+  "type": "object"
+}

removedInput schema / required
```
Removed value: -[
-  "subjectKind"
-]
```

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already flag destructive/non-idempotent/open-world, and the description adds genuinely new behavioral facts: one paid GPT Image 2.5 generation capped at 5/day, existing artwork retained until replacement succeeds, and that defaults 'never republish a strategy or alter existing publications' with explicit per-publication choices winning. The cost/rate-limit disclosure is the kind of context annotations cannot carry.

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?

Front-loaded with the core action, but the publishingDefaults sentence ('To save your default positions, filled-trade and open-order sharing for first-time strategy publications, pass publishingDefaults alone: policy contains those three booleans...') is a run-on that is hard to parse on first read. For a 22-parameter tool the length is defensible, but the structure obscures the special mode rather than clarifying it.

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?

Covers the special defaults-only mode, the publish-after-save flag, the artwork regeneration trade-off, and the account-vs-strategy content distinction, which is substantial for a tool this complex. Gaps remain: with zero required parameters and no output schema, the description never says which fields identify the subject or what a successful save returns (draft id, URL, publication record).

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

Parameters3/5

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

Schema description coverage is only 23% across 22 params, so the description has to compensate, and it does for the hardest part — the nested publishingDefaults object (policy's three booleans, excludedNameContains as case-insensitive literal name phrases) and regenerateHeroImage. It says nothing about accountId/strategyId/subjectKind exclusivity, tags, title, details, or the many allow*View toggles, leaving most parameters undocumented in both places.

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?

Opens with a specific verb+resource: 'Creates or updates a draft for exactly one explicit subject,' and later clarifies that an account publication contains no strategies while a strategy publication contains only that strategy. That distinguishes it from the sibling publish_to_marketplace/unpublish_from_marketplace tools by scope, though it never names them directly.

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

Usage Guidelines3/5

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

Gives conditional guidance for one mode ('To save your default positions... pass publishingDefaults alone') and routes reads to my_marketplace_publications(action="list"). It does not state when to use this versus publish_to_marketplace, unpublish_from_marketplace, or update_strategy, so the main routing decision 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 BotSpot: AI Trading, Backtests and Bots 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.